I ran some tests and it appears that SSL affects IE 11 such that PTST is added to user string on HTTP, but not for HTTPS, I’m guessing because of browser security limitations?
Interestingly enough CHROME and SSL still work and PTST is being added
(split into a new thread)
Thanks. Should be easy enough to fix. Right now most of the header manipulation is done at the socket level which has access to all unencrypted data but doing the same for HTTPS data is a bit more difficult.
In the Chrome agent we use the command-line and an extension to modify the UA string so it can modify HTTPS requests. For IE we have the ability to see all HTTP requests before they are generated and can change the UA string there. I’ll see if I can carve out a few minutes later this afternoon to fix it.
It should only take 1-2 lines of code here: https://github.com/WPO-Foundation/webpagetest/blob/master/agent/wpthook/hook_wininet.cc#L620
Awesome! Thanks Pat.
Should be all fixed now: http://www.webpagetest.org/result/160519_QS_22d3e6cf2cf4c46347a1a5f75358716a/1/details/#request1