215955 - composer incorrectly performs HTTP PUT on cgi scripts

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[paul]

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

If you try to edit CGI-generated page using PUT method, say
http://some.server.com/cgi-bin/page.pl?name=John
composer tries to publish it as file /cgi-bin/page.pl
But web-server in case of CGI-pages doesnt use standard PUT script - it sends
PUT to /cgi-bin/page.pl. If page.pl is able to handle PUT, it would be nice and
easy way to content management. Unfotunately, Mozilla behaves badly in such case:
1) All parameters after '?' stripped
2) Associated files (stylesheets, images etc) looses path. For example,
styleshhet linked as <link rel=stylesheet href="/style.css"> tried to publish
not in root folder, it publishes in the same folder as page.pl. And more, it
publishes as CGI-script, so no executable file /cgi-bin/style.css - no publishing.

Reproducible: Always

Steps to Reproduce:
See above


Expected Results:  
1. Dont strip parameters for QUERY_STRING
2. Use correct path for associated files

Comment 1

[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 2

[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.