search

t-artistik / browserscope

Automatically exported from code.google.com/p/browserscope
Apache License 2.0
0 stars 0 forks source link

IE9 PP4 can't finish the network tests #242

Closed GoogleCodeExporter closed 8 years ago

GoogleCodeExporter commented 8 years ago 
What steps will reproduce the problem?
1. Run IE 9 PP4
2. Start the Network tests
3. 500 on test 11 - Cache expires

Looking in the logs, it looks like whatever sends IE9 to the cache expires test 
is sending it to the wrong URL..

08-08 08:17PM 23.022 /cache-expires2?t=1281323832 500 130ms 80cpu_ms 
21api_cpu_ms 0kb Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; 
Trident/5.0),gzip(gfe),gzip(gfe)
08-08 08:17PM 12.238 /network/tests/cache-expires?t=1281323639 200 86ms 
101cpu_ms 43api_cpu_ms 0kb Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; 
Trident/5.0),gzip(gfe),gzip(gfe)
08-08 08:13PM 31.118 /network/tests/cache-expires2?t=1281323606 200 93ms 
101cpu_ms 43api_cpu_ms 0kb Mozilla/5.0 (X11; U; Linux x86_64; en-US) 
AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.125 
Safari/533.4,gzip(gfe),gzip(gfe)
08-08 08:13PM 26.495 /network/tests/cache-expires?t=1281323522 200 90ms 
101cpu_ms 43api_cpu_ms 0kb Mozilla/5.0 (X11; U; Linux x86_64; en-US) 
AppleWebKit/533.4 (KHTML, like Gecko) Chrome/5.0.375.125 
Safari/533.4,gzip(gfe),gzip(gfe)
08-08 08:12PM 11.695 /cache-expires2?t=1281323527 500 143ms 80cpu_ms 
21api_cpu_ms 0kb Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; 
Trident/5.0),gzip(gfe),gzip(gfe)
08-08 08:12PM 07.336 /network/tests/cache-expires?t=1281323282 200 86ms 
62cpu_ms 43api_cpu_ms 0kb Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; 
Trident/5.0),gzip(gfe),gzip(gfe)
08-08 08:11PM 56.107 /cache-expires2?t=1281323511 500 52ms 80cpu_ms 
21api_cpu_ms 0kb Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; 
Trident/5.0),gzip(gfe),gzip(gfe)

Original issue reported on code.google.com by els...@gmail.com on 9 Aug 2010 at 3:20

GoogleCodeExporter commented 8 years ago 
I wonder if it's this piece of code in cache-expires.html:

<script>
window.onload = function() {
    parent.testframe.location = "cache-expires2?t={{ epoch }}"
}
</script>

It seems that IE9 PP4 is taking the location path as an absolute path and then 
hitting a 500. This seems like incorrect behavior.. should we just hardcode the 
/network/tests/cache-expires2?t={{ epoch }} path there maybe?

Original comment by els...@gmail.com on 9 Aug 2010 at 3:22

GoogleCodeExporter commented 8 years ago 
I finally got IE9 PP4 installed and am debugging. Sure enough, in test 11 
(Cache Expires) it does a request for:
    http://www.browserscope.org/cache-expires2?t=1281980601
when what we really want is:
    http://www.browserscope.org/network/tests/cache-expires2?t=1281980601

But if we hardcode the path, will that still work in other instances (appspot 
and local dev box)?

Original comment by stevesou...@gmail.com on 16 Aug 2010 at 5:46

GoogleCodeExporter commented 8 years ago 
So I tested locally, and it fixes IE PP to do location.href = 'relativepath' - 
previously the file was doing location = 'relativepath' and that was turning 
into an absolute path. Pushing..

Original comment by els...@gmail.com on 17 Aug 2010 at 11:17

GoogleCodeExporter commented 8 years ago 
This issue was closed by revision r683.

Original comment by els...@gmail.com on 17 Aug 2010 at 11:19