Current time: 12-10-2019, 05:38 PM Hello There, Guest! (LoginRegister)

Post Reply 
 
Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5
The latest version (54.0.2840.71) Chrome doesn't work for HTTPS request
11-01-2016, 12:49 PM (This post was last modified: 11-02-2016 12:44 PM by sally.)
Post: #1
The latest version (54.0.2840.71) Chrome doesn't work for HTTPS request
Recently, I found the Chrome doesn't work for HTTPS requests any more on my private instance. And I checked there's a new version released (54.0.2840.71) for Chrome. I tried reverting back to version 53 and it works. So there should be something wrong with the latest version. Please help check.
Find all posts by this user
Quote this message in a reply
11-02-2016, 05:33 AM
Post: #2
RE: The latest version (54.0.2840.71) Chrome doesn't work for HTTPS request
What version of the agent are you running? You probably need to update wptdriver: https://sites.google.com/a/webpagetest.o...est-Agents
Visit this user's website Find all posts by this user
Quote this message in a reply
11-02-2016, 12:43 PM (This post was last modified: 11-02-2016 12:49 PM by sally.)
Post: #3
RE: The latest version (54.0.2840.71) Chrome doesn't work for HTTPS request
(11-02-2016 05:33 AM)pmeenan Wrote:  What version of the agent are you running? You probably need to update wptdriver: https://sites.google.com/a/webpagetest.o...est-Agents

Thanks. After updating to the latest version, it's working.

BTW, is there any way to subscribe the updates so I can always get the the latest version?

In addition, once I update the agent, the Firefox template file (agent/templates/Firefox/prefs.js) is overwritten. I have to manually update it (add proxy settings) again after updates for all agents. Any better suggestion?
Find all posts by this user
Quote this message in a reply
11-04-2016, 10:05 PM
Post: #4
RE: The latest version (54.0.2840.71) Chrome doesn't work for HTTPS request
There is an "agentUpdate" setting in settings.ini that you can set that will automatically check for (and install) updates hourly: https://github.com/WPO-Foundation/webpag...ample#L118

If you have a custom prefs then you will either need to update the wptupdate.zip package (extension.zip has the templates folder) or all tests would need to use a script that set the prefs explicitly.

If you want to open a github issue I can see about adding support for server-specified firefox prefs that get added to every test automatically.
Visit this user's website Find all posts by this user
Quote this message in a reply
Post Reply 


Forum Jump:


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