The client initiates the session and specifies the HTTP protocol. The server should then comply with the requested protocol. Unless there is a bug with Tomcat or Jetty - you haven't specified the servlet container to which you are connecting. You should check the transmission streams using an appropriate stream listener.
Well, i am using tomcat as a servlet container, and let me explain my problem in more details;
i have installed the web server and the DB on my local machine for development time and i have no problem with the HTTP protocol version which is 1.1.
at the same time i have the same copy of both the web server and DB on the server.
but when i am testing the same page locally and online from the same machine and the same browser
version which spicifying the HTTP version i am getting two different versions 1.0, 1.1.
and simply i need to use the 1.1 version because of the expiry and caching issues in version 1.0 are buggy
So could you plz help me!!
And could you plz explain what do you mean by
"You should check the transmission streams using an appropriate stream listener"
or how should i do that !!
You would use WinpDump or tcpdump, or a similar sniffer depending on whether you are Windows or *nix based. Since the initiation of the HTTP protocol version should be initiated by the client (browser usually), you would be looking at the request for the protocol version specified. That you are getting different results based on on-line versus local would indicate something such as a firewall-proxy being involved and changing the HTTP version received by the server. But you would need to ascertain that. However, this is known to occur with older proxy servers or load-balancing proxy farms.
In any case, you are looking for conditions in the transmissions that indicate when the HTTP version changes and who changes it.