Was there an API change resulting in PTST no longer appearing for HTTPs requests?
|
09-19-2015, 01:10 AM
(This post was last modified: 09-19-2015 02:16 AM by shmilla.)
Post: #1
|
|||
|
|||
Was there an API change resulting in PTST no longer appearing for HTTPs requests?
Has something changed in the last couple of months? We used to see the PTST get added to the user agent string, but I just ran some test cases where it does not. Some people use the PTST to filter webpagetest scripts for some analytics so I was asked to look into this. I've made no changes to our scripts, however it seems to have disappeared when using an API call. Looking into it, the issue seems to happen on HTTPs only. You'll note my scripted API calls below don't use "keepua", so I would expect it to be there.
On HTTPS we don't see it http://www.webpagetest.org/result/150918...1/details/ API Call Example to reproduce Code: GET http://www.webpagetest.org/runtest.php?f=xml&k=(deleted)&video=1&bwDown=20480&bwUp=5120&latency=4&plr=0&priority=3&fvonly=1&maxruns=50&runs=1&location=Dulles:Chrome.custom&block=.flv+.mp4&private=1&ignoreSSL=1&label=FEO-ON&noopt=1&sensitive=0&standards=on&pngss=1&script=setHeader%09Pragma%3a+akamai-x-feo-trace%0d%0ablock%09.flv+.mp4%0d%0anavigate%09https%3a%2f%2fwww.google.com%2f%0d%0a HTTP/1.1 On HTTP we do see it http://www.webpagetest.org/result/150918...1/details/ API Call Example to reproduce Code: GET http://www.webpagetest.org/runtest.php?f=xml&k=(deleted)&video=1&bwDown=20480&bwUp=5120&latency=4&plr=0&priority=3&fvonly=1&maxruns=50&runs=1&location=Dulles:Chrome.custom&block=.flv+.mp4&private=1&ignoreSSL=1&label=FEO-ON&noopt=1&sensitive=0&standards=on&pngss=1&script=navigate%09http%3a%2f%2fwww.google.com%2f%0d%0a HTTP/1.1 |
|||
« Next Oldest | Next Newest »
|
User(s) browsing this thread: 1 Guest(s)