Closed
Bug 197585
Opened 23 years ago
Closed 23 years ago
"Publish" incorrectly reports failed first save (Apache 1.3x Linux, publishing over SSL) https
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: ind.bugz01, Unassigned)
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030307
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4a) Gecko/20030307
The first time I publish a new file with composer, I get the red "X" and the
message that the save failed. However, the file is saved.
The second time I publish, I have to re-enter the file name (since composer
thinks it hasn't saved yet).
Thereafter, it both publishes properly and reports properly.
I'm using Apache 1.3x on Linux, publishing over SSL (haven't tried without it).
Reproducible: Always
Steps to Reproduce:
create new file with composer
publish via https (make sure file by same name does not already exist on server)
Actual Results:
composer incorrectly reports that publishing failed, and forgets filename
Expected Results:
Recognized that the save succeeded and report it crrectly, and remember filename.
Comment 1•23 years ago
|
||
Darin--any clue what caused this bug?
Summary: "Publish" incorrectly reports failed first save → "Publish" incorrectly reports failed first save (Apache 1.3x Linux, publishing over SSL) https
Comment 2•23 years ago
|
||
reporter (lloyd)--can you test this with a newer build? 1.4beta or a nightly
from the 1.4 branch?
Comment 4•23 years ago
|
||
-->worksforme per comment 3
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•