Closed Bug 260099 Opened 20 years ago Closed 20 years ago

Firefox 1.0 PR sends requests as HTTP 1.0

Categories

(Core :: Networking: HTTP, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: mikus, Assigned: darin.moz)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 I tried various websites and for all of them Firefox sends HTTP 1.0 request. This is particularly problematic for me, because I need to set Cache-Control: no-store, which appeared in HTTP 1.1 spec. On the other hand, Pragma: no-cache used in HTTP 1.0 does not force Firefox to reload a page on back. Of course, I can set Cache-control header without analyzing HTTP version, but this does not seem clean, does it? Reproducible: Always Steps to Reproduce: I used Naviscope 8.70 to sniff HTTP requests and responses. Each time it shows "Browser to Naviscope" as HTTP 1.0. Actual Results: GET HTTP 1.0 Expected Results: GET HTTP 1.1
> Firefox sends HTTP 1.0 request. I have Advanced Preferences Configuration plugin, which shows network.http.version as 1.1
MSIE 6.0 has two options: * Use HTTP 1.1 * Use HTTP 1.1 through proxy connections With "Use HTTP 1.1" turned ON and "Use HTTP 1.1 through proxy connections" turned OFF Naviscope log shows the following request from MSIE6.0: === cut here === From Browser to Naviscope www.google.com:80/ Fri Sep 17 11:31:58 2004 GET http://www.google.com/ HTTP/1.0 Accept: */* Accept-Language: en-us Pragma: no-cache User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461) Host: www.google.com Proxy-Connection: Keep-Alive === cut here === With "Use HTTP 1.1" turned ON and "Use HTTP 1.1 through proxy connections" turned ON Naviscope log shows the following request from MSIE6.0: === cut here === From Browser to Naviscope www.google.com:80/ Fri Sep 17 11:23:09 2004 GET http://www.google.com/ HTTP/1.1 Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, application/msword, application/vnd.ms-excel, application/vnd.ms-powerpoint, application/x-shockwave-flash, */* Accept-Language: en-us Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461) Host: www.google.com Proxy-Connection: Keep-Alive === cut here === With "network.http.version" set to "1.1" Naviscope log shows the following request from Firefox 1.0 PR: === cut here === From Browser to Naviscope www.google.com:80/ Fri Sep 17 11:34:06 2004 GET http://www.google.com/ HTTP/1.0 Host: www.google.com User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 Accept: text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5 Accept-Language: en-us,en;q=0.5 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 300 Proxy-Connection: keep-alive === cut here === The issues are: * Despite network.http.version set to 1.1 Firefox uses HTTP 1.0 request type. * If Firefox behaves differently when a proxy is present, this behavior cannot be controlled (see MSIE options earlier). By the way, why User-Agent states that Firefox is still 0.10 ?
what is naviscape and how does it work? > * If Firefox behaves differently when a proxy is present, this behavior cannot > be controlled (see MSIE options earlier). That is wrong, it can be controlled. The default is (I think, I don't use firefox) to use 1.1 over a proxy too, though. see about:config, network.http.proxy.version > By the way, why User-Agent states that Firefox is still 0.10 ? that's the internal version number of 1.0preview
Note that you can sniff the traffic from the firefox end (without a proxy) using the steps described at http://www.mozilla.org/projects/netlib/http/http-debugging.html
Christian: Naviscope is a nice caching/proxy/ad-removing utility, its development stopped about 3 years ago. I downloaded nightly Mozilla 1.8a4, Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8a4) Gecko/20040920. It has clear settings about HTTP 1.0/1.1 for direct connection and for connection through proxy. The setting works correctly. Firefox 1.0PR, Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20040913 Firefox/0.10 does not have this setting available from regular options dialog (as well as caching settings which I needed before). These important settings are available only through Preferential extention, I used Preferential 0.6.1a from 2003-11-30. Christial is right, network.http.proxy.version works properly, by default it configured to HTTP 1.0. I would like that important properties were accessible through regular options interface, not through some geeky extention. This bug can be closed. By the way, what is favicon.ico? Firefox asks for it from every website, Mozilla does not do that.
thanks, marking invalid per last comment. >I would like that important properties were accessible through regular options >interface, not through some geeky extention. feel free to file a bug on firefox about that. >By the way, what is favicon.ico? Firefox asks for it from every website, Mozilla >does not do that. (mozilla can do it if you set a hidden pref). since MSIE uses /favicon.ico to show an icon next to bookmarks, ffox searches for that to display it in tab titles, bookmarks, etc.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.