Publication reports error after 307 (Temporary Redirect) when in fact it worked.



12 years ago
7 years ago


(Reporter: paul, Unassigned)


SeaMonkey 1.1 Branch

Firefox Tracking Flags

(Not tracked)




12 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv: Gecko/20070219 Firefox/
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv: Gecko/20070221 SeaMonkey/1.1.1

If on PUT, Composer gets a response back from the server to do Temporary Redirect (307), it does attempt to publish the item to that location.

The publication works (after a warning dialog), but Composer reports that it did not. Erroneously.

Response was actually:

HTTP/1.1 204 No Content

Date: Mon, 05 Mar 2007 02:00:39 GMT
Server: Apache/2.0.52 (Red Hat)
Content-Length: 0
Keep-Alive: timeout=15, max=99
Connection: Keep-Alive
Content-Type: text/plain; charset=UTF-8

Reproducible: Always

Steps to Reproduce:
1. GET a page from a location in SeaMonkey's browser side.
2. initiate edit
3. publish back (the server in question issues 307 redirect in response to the PUT).
4. click through the warning dialog.

Actual Results:  
error dialog ("publication failed") AND item arrived intact

Expected Results:  
item arrives intact

This behavior is due to the redirect.

If you (on publication) select the redirect URL by hand as part if the publications settings dialog, the item arrives fine and there is no error dialog.

Different upload sites are very common for web application/sites that have not upload.
Can you reproduce with SeaMonkey v1.1.9 ?
Version: unspecified → SeaMonkey 1.1 Branch
Assignee: composer → nobody
QA Contact: composer

Comment 2

7 years ago
Could you confirm if this still happens on SM2.3?
OS: Mac OS X → All
Hardware: PowerPC → All
Version: SeaMonkey 1.1 Branch → Trunk


7 years ago
Version: Trunk → SeaMonkey 1.1 Branch

Comment 3

7 years ago
Paul, do you still see this problem?
Whiteboard: closeme INCO 2012-08-01

Comment 4

7 years ago
Resolved per conversation in e-mail, reporter no longer able to recheck this problem.
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
Whiteboard: closeme INCO 2012-08-01
You need to log in before you can comment on or make changes to this bug.