NetTalk Central
NetTalk Web Server => Web Server - Ask For Help => Topic started by: Larry Sand on August 13, 2009, 12:16:30 PM
-
When running Fiddler with IE and you click on a browse line with highlighting as the selection method fiddler pops and error message:
Fiddler has detected a protocol violation in session #1.
The Server did not return properly formatted HTTP Headers. Maybe missing altogether (e.g. HTTP/0.9), maybe only \r\r instead of \r\n\r\n?
----------------
This was using example 47 and NT 4.36 and it does not occur on FireFox. I tested in IE 6, 7, and 8.
Here are the headers:
Request
===============
GET /mailboxesbrowsecontrol?&_ParentProc=&_Clicked=1&id=MAI:MailBoxNumber&Value=2&_rnd_=0.4852343367848425&_= HTTP/1.1
Accept: */*
Accept-Language: en-us
x-prototype-version: 1.4.0
Referer: http://192.168.67.85:81/index.htm
x-requested-with: XMLHttpRequest
x-rico-version: 1.1.0
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.0; WOW64; Trident/4.0; SLCC1; .NET CLR 2.0.50727; InfoPath.2; .NET CLR 3.5.21022; .NET CLR 3.5.30729; .NET CLR 3.0.30729; MS-RTC LM 8)
Host: 192.168.10.85:81
Connection: Keep-Alive
Cookie: SESSIONID=1969143644
Response
===============
HTTP/1.0 200 This buggy server did not return headers
Larry
-
>> HTTP/1.0 200 This buggy server did not return headers
Ouch! Why doesn't it say what it really thinks! <g>
This was quite a hard one to track down, but of course was really simple when it was. I've included the fix in the 4.37 build - but if you want to correct in your current build follow the instructions below.
In \clarion6\libsrc\netweb.clw
a) at the end of the ProcessRequest method, add a line
self._CloseConnection()
b) at the end of the _HandleGetRest method remove the call to
self._CloseConnection()
Thanks for the report Larry.
cheers
Bruce
-
>> HTTP/1.0 200 This buggy server did not return headers
Hehe, I thought you might like that error msg. There are some funny ones in there. The protocol checking of this proxy is great. It pointed out an error that I had in a webservice client in my calculation of the content length.
I made the changes and can confirm that fixes the problem.
Thanks much,
Larry