CL1 webserver: <Anantsystems<Ad info>

    AspnetEmail.com   AspNetPro.com

related sites: <FREE Help> <ASP> <Asp.net> <worldwide>  
feedback: <lovethat> <hatethat> <thanks> <credits> <contact us>

UNSOLVED! HTTP Header Problem Table of Contents PrintView CL1
<Previous> UNSOLVED! Server Application Error

UNSOLVED! Jolt corrupting data retrieval <Next>


       


From: Bill Zack <wzack@csi.com>
Subject: [asp advanced] ASP HTTP Protocol Problem?

Using Peter Genusa's outstanding HTTPSPY ISAPI filter to  troubleshoot some ASP problems on our web server we noticed the  following oddity.

A browser program written to identify itself as an HTTP 1.0  browser connects to our web server.

When the server responds it seems to be responding with HTTP  1.1 protocol components. RFC 1945 states that the server  should downgrade itself to HTTP 1.0 in this case.

Is this a problem? If so, how can we force the web server to reply with 1.0 protocol?

(An extract of the HTTP headers are shown below.)


Thanks for any help that you might be able to provide.
Bill Zack
wzack@compuserve.com

----------------- http extract -----------------------
4/13/98 4:20:50 PM--SF_NOTIFY_READ_RAW_DATA
POST /fctcigw/EQACDS.ASP HTTP/1.0
Host: 147.118.7.253
User-Agent: Mozilla/3.01 (WinNT;I)
Content-Length: 115
Content-Type: application/x-www-form-urlencoded

txtIssue=07210&txtAccount=00790000140&txtSSN=232115001&txtPWD=newpass&txtNew
PWD=&txtTransactionID=ACDS&whichserver=
Connection: Keep-Alive
Cookie: ASPSESSIONIDQGQQGQCR=ICILCMABNKOHHEADBBDAIHBF

CL1 webserver: <Anantsystems<Ad info>

    AspnetEmail.com   AspNetPro.com

related sites: <FREE Help> <ASP> <Asp.net> <worldwide>  
feedback: <lovethat> <hatethat> <thanks> <credits> <contact us>