Thread

Hi, widesky—

To further troubleshoot this, could you send an email (not PM) with the following details:

* FTP URL
* FTP ID and Password
* URL to this thread

Thank you.

Ok, all sent.

Alright, we’ve had a look at this.  I’ve emailed you a link to a test file.

The server is sending the cookie in the headers; to track down why its doing this you would need to ask your host to trace it.  The file I’ll send will prove its existence, so you can send that link to your host.

Let us know what they say.

This is what the hosting provider said about the cookie being set:

Our Apache web server is configured such that it sets the HTTP_COOKIE
value on the server whenever there is a request sent to the server.

That still doesn’t really explain why it’s sending out cookies of its own. The only instance I know of where Apache automatically sets a cookie on every request is using the mod_usertrack module and the CookieTracking directive. Is your host doing that?

You could try turning it off in your .htaccess:

CookieTracking off

Ingmar,

I asked them why they are setting it and what I can do to override it… haven’t heard back yet.

The .htaccess override does not seem to work.

Actually, it was only a hypothesis at this point. Either way, let us know what they say.

Even if the .htaccess trick worked, it would be important to ask them why they’re setting a server-wide cookie, and if they allow it to be switched off.  This is definitely something to follow up with them on.  Please keep us updated.

After checking your phpinfo() file, I can confirm that mod_usertrack is compiled in and loaded. This means that Apache is automatically setting a cookie on every page request. Please do take this issue up with your host, as there is really nothing we can do about it. Thank you.

I am waiting on the client’s hosting provider to return my question about the setting.

Out of curiosity, why would a host have mod_usertrack loaded to always set a cookie, and what specifically about this is messing with EE.

Thanks for the continued help.

The cookie key is being set with a dollar sign, which is something that ExpressionEngine filters out for security reasons.

As to why your host would use that - it’s a very good question, but only your host can answer.  Let us know what they say =)

Hi, widesky - I just wanted to follow up here and see if you had heard anything more from your host, and if this was now fixed up for you. =)

I do not know what to say about this… we ended up switching hosting providers and everything worked just fine.  So it goes…

For the record, the hosting company never answered the questions everyone recommended that I ask, so I don’t have any more insights into what was causing the problems.

Thanks for the help though!

Thanks for the update, widesky.  Glad you found a resolution, and I’m sorry it didn’t work out with your previous host.  That can be very frustrating, but at least you’re up and running now!