Cookie Problem

[milge]

Hi There,

I’m gonna migrate my site to Pagely.com. But their support team said i can not use it. You can see what they said:

“I see a cookie is being generated: Set-Cookie: WdhzEx=1; expires=Sun, 21-Feb-2016 22:15:20 GMT; Max-Age=10800

Any plugin or theme that creates a PHP session will break caching with a session present. What that means is that potentially, a single page could have different content for each visitor and it would be dangerous to generate a page once and then serve it from cache to two different visitors. Thus, every single page request would not be cached. However, having your site hit our cache layer is important since that is the first thing you’d want to make sure when optimizing your site for scalability.

This looks to be created by the hide_my_wp plugin so you really should remove it since it will hurt your site when you see higher traffic levels.”

I wait your comments immediately. Cause i can not use plugin right now.

Thanks,
Bilgehan

[Suman M.]

Hi, there are many plugins that generates cookie/session and HMWP is compatible with cache plugins like wp super cache, w3 total cache, etc.
However, I’ve forwarded this ticket to sr. support so that he can better look into it.

[Hassan]

Hello,

Simply disable full hide mode (general tab) to avoid that kind of cookie.

It may still create that cookie but it’s not functional and can’t invalidate caches.

[milge]

I have disabled full hide mode to partial mode. But they warn me it still create cookie.

HTTP/1.1 200 OK
Server: openresty/1.9.7.1
Date: Mon, 22 Feb 2016 23:21:57 GMT
Content-Type: text/html; charset=UTF-8
Connection: keep-alive
Keep-Alive: timeout=30
Link: <http://s16237.p413.sites.pressdns.com/wp-json/&gt;; rel=”https://api.w.org/&#8221;, <http://wp.me/P6JuQV-6&gt;; rel=shortlink
Set-Cookie: WdhzEx=1; expires=Tue, 23-Feb-2016 02:21:57 GMT; Max-Age=10800
Vary: Accept-Encoding, User-Agent
X-User-Agent: standard
X-Cache-Config: 0 1
X-Cache-Status: BYPASS

[Hassan]

Well, full hide mode is totally different with full replace mode! It’s a check option.

As I said it may still create that cookie but it’s not functional. If it’s important to not create that cookie you need to edit our source code.

Open load.php in HMWP directory and change following lines in the top of that:

if (!isset($_GET['style_wrapper']))
    setcookie($this->access_cookie(), 1, time() + 60 * 60 * 3);//3 hours

With this:

if (!isset($_GET['style_wrapper']) && $this->opt('full_hide'))
    setcookie($this->access_cookie(), 1, time() + 60 * 60 * 3);//3 hours

This was added to our upcoming update, too.

[milge]

Yes, solved! Thank you for great support!

[Author]

Posts