Current time: 08-19-2017, 10:02 AM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
setCookie not working any more
04-06-2017, 09:43 PM
Post: #1
setCookie not working any more
Hi, I was using the 'setCookie' property to bypass a cookiewall on my tests, and it stopped working a few days ago. I didn't change anything, I think some change was introduced on the server, seeing the recent github commits.

It stopped working around 4th april 14h GMT.
I'm using Amsterdam, NL - IISpeed - Firefox - Native

Thanks !
Find all posts by this user
Quote this message in a reply
04-07-2017, 03:58 AM
Post: #2
RE: setCookie not working any more
I think i may be suffering from this too ... i ran a script about a month ago which had a 'setCookie' command and it worked but the same script doesn't work right now ...
I'm using a private instance with agents running on version 371 (same as public wpt agents)
Note: I tried both Chrome and Firefox - same issue
Find all posts by this user
Quote this message in a reply
04-07-2017, 05:58 PM
Post: #3
RE: setCookie not working any more
Yeah, I think is a bug introduced on the latest release. Let's just wait for Patrick to take a look Smile
Find all posts by this user
Quote this message in a reply
04-08-2017, 03:07 AM
Post: #4
RE: setCookie not working any more
This issue appears to have been raised as a bug on the WPO github: https://github.com/WPO-Foundation/webpag...issues/844

Follow me on twitter: @rakshay
Visit this user's website Find all posts by this user
Quote this message in a reply
04-26-2017, 11:21 PM
Post: #5
RE: setCookie not working any more
Hi, I just discovered that the problem is happening only in Firefox. Here are two exact tests with scripting, setting a cookie to remove the cookie bar (on the top of the screenshot):

- Chrome https://www.webpagetest.org/result/170426_C6_Z75/
- Firefox https://www.webpagetest.org/result/170426_CQ_Z4V/
You can see the setCookie worked on Chrome but not on Firefox.

I see something different, though, if I use the API (npm), but it also fails. I think this functionality needs to be reviewed with the update.

Thanks
Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


User(s) browsing this thread: 3 Guest(s)