(argh) STEPS: publish to directory where the web server does not have local write access (in this case, a Solaris server w/ fast track). OBSERVED: vague error "unknown publishing error occurred". EXEPCTED: This is http. the error codes are well understood, in this case the server log shows: "PUT <filename> HTTP/1.0" 403 142 (it sent back a 403 HTTP error) the error log shows: "upload-file reports: can't write to /export/home/docs/pktg/docs/net/snoop/ftp.snoop.html (No access rights)"
This same error is occuring with AIX.
Summary: Publish error: http 403 error is "unknown publishing error occurred" → Publish: http 403 error is "unknown publishing error occurred"; want more specific error message
Assignee: composer → nobody
QA Contact: chrispetersen → composer
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614
Status: NEW → UNCONFIRMED
MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.