219341 - Some cgi parameters are not correctly recognized by the browser

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[sturman]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827

Mozilla does not "translate" and send to the HTTP server some (eventual) cgi
parameters received from the server that have been coden in HEX.
An example:
The Union catalogue of the Venice city (Italy) libraries
(http://194.243.104.179/html/NautaStart.htm) uses an cgi application called
wwwisis (www.bireme.br) that is submitted to the http server in this format:
http://.../wwwisis.exe /[in=...]/?...

When the Mozilla browser receives the http document (e.g. a form) the above
mentioned square brackets are coded (by the http server) in HEX, but Mozilla
does not "translate" them back in "[]" when the form is submitted to the http
server. IE and Netscape handle this translation process correctly.

The incorrect "translation" regards only the part of parameters send from the
browser to the http server BEFORE the first "?".


Reproducible: Always

Steps to Reproduce:
1. select from the top menu "Catalogo"
2. select from the top menu "Libera"
3. Enter in the "immetti la string di ricerca" the string "Fermi" and press the
"Esegui" button
4. The "Server internal error" or a blank page is displayed

Re-execute the same search with IE or Netscape (no errors are dsplayed)

Actual Results:  
4. The "Server internal error" or a blank page is displayed

Expected Results:  
a list of retrieved records

Comment 1

[Olivier Cahagne]

shorter steps to reproduce:
1. Load http://194.243.104.179/html/NautaRicLibera.htm
2. Enter "Fermi"
3. Press "Esegui"

Has this ever worked with Mozilla, if so, what was the last build working with
this form ?

Comment 2

[Boris Zbarsky [:bzbarsky]]

CGI parameters are processed by the SERVER, not the client.  And the server
needs to be able to deal with both the escaped and unescaped versions of
characters, since both represent the same URI.

It sounds like IE does not escape '[' and ']' in URIs and we do.  Darin,
andreas, was there a good reason for that?  If so, this is probably evangelism...

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.