Index
> Windows > IE9 weird socket issue |
| Author |
|
|
sleepsleep 17 Feb 2013, 18:04
maybe you got some experience dealing with IE9, i have a weird issue.
let me show you how my server interact with quetannon, so we got some idea how things works. Code: [A] s[216] [R] s[216] ----------------------------------- recv : 29 bytes hello world from quetannon. [C] s[216] i start the server, open IE9, browse to http://localhost, stop the browser, and then finally close the browser. Code: [A] s[212] [A] s[220] [R] s[220] ----------------------------------- recv : 239 bytes GET / HTTP/1.1 Accept: text/html, application/xhtml+xml, */* Accept-Language: en-us User-Agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.0; Trident/5.0) Accept-Encoding: gzip, deflate Host: localhost Connection: Keep-Alive s[220] WSAGETSELECTERROR - 0X2745 [C] s[220] s[212] WSAGETSELECTERROR - 0X2745 [C] s[212] if i didn't close the browser, socket s[212] wouldnt get closed why IE9 make 2 sockets connection, either one send GET, another one sent nothing. firefox pattern Code: [A] s[212] [R] s[212] ----------------------------------- recv : 284 bytes GET / HTTP/1.1 Host: localhost User-Agent: Mozilla/5.0 (Windows NT 6.0; rv:18.0) Gecko/20100101 Firefox/18.0 Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate DNT: 1 Connection: keep-alive [C] s[212] |
|||
17 Feb 2013, 18:04 |
|
|
sleepsleep 18 Feb 2013, 11:03
wow, i think that is beyond my capability, =(
optimization, maybe, i notice for 2 attempt to access http://localhost on 2nd tab, it uses the s[212] socket, maybe this is designed by IE team, probably, i guess, i will try force close the socket and see if IE crashed. |
|||
|
18 Feb 2013, 11:03 |
|
< Last Thread | Next Thread > |
Forum Rules:
|