Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#10767 - Minefield / Firefox 3.0 HTTP POST REQUEST failure

Attached to Project: Arch Linux
Opened by Daniele Stanzani (stanza) - Friday, 27 June 2008, 11:12 GMT
Last edited by Jan de Groot (JGC) - Monday, 30 June 2008, 07:38 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture i686
Severity Low
Priority Normal
Reported Version 2007.08-2
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I don't know it it a bug or not, or if it depends o my web server.

When i send a gzip compressed file with the browser, the header is

application/gzip,
not application/x-gzip, that i suppose, from my googling around, should be the right choiche.

Additional info:
* package version(s)
* config and/or log files etc.


Steps to reproduce:

Send a gzip compressed file over a form post and check the client HTTP headers.
This task depends upon

Closed by  Jan de Groot (JGC)
Monday, 30 June 2008, 07:38 GMT
Reason for closing:  Upstream
Additional comments about closing:  See last comment from Aaron.
Comment by Jan de Groot (JGC) - Friday, 27 June 2008, 11:53 GMT
Both mimetypes are valid for gzipped data, so this isn't a bug AFAIK.
Comment by Daniele Stanzani (stanza) - Friday, 27 June 2008, 12:35 GMT
I suppose apache 2 comes with default
AddType application/x-gzip .gz .tgz

that means the content-type for a gzip compressed application is application/x-gzip.

This obviously does not mean that the standard specs states that that content-type is the default one, but I cannot find any specs or RFC regarding this issue.
Comment by Aaron Griffin (phrakture) - Friday, 27 June 2008, 15:43 GMT
This sounds like an upstream bug if it's a bug at all. I recommend you report this to the mozilla team

Loading...