Web Server Scripting Hack to Maintain State and Keep a Domain Cookieless

Posted by jasonspalace on Server Fault See other posts from Server Fault or by jasonspalace
Published on 2010-02-09T00:08:27Z Indexed on 2010/03/21 15:01 UTC
Read the original article Hit count: 523

Filed under:
|
|
|
|

Hello, I am looking for a solution on a LAMP server to keep a site cookieless such as "example.com", where static content is served from "static.example.com", and with rules in place to rewrite requests for "www.example.com" to "example.com". I am really hoping to avoid setting up a cookieless domain for the static content due to an unanswered SEO concern with regards to CNAMEing to a CDN. Is there a way, (or safe hack), that can be implemented where a second domain such as "www.example2.com" is CNAMEd, aliased, or otherwise used with "example.com" to somehow trick a php application into maintaining state with a cookie dropped on "www.example2.com" therefore keeping all of "example.com" cookieless?

If such a solution is feasible, what implications would exists with regards to SSL and cross-browser compatibility other than requiring users to accept cookies from 3rd party domains and possibly needing an additional SSL to keep the cookie secure?

Thanks in advance to all.

© Server Fault or respective owner

Related posts about cookieless

Related posts about lamp