207541 - Publishing via proxy server does not display proxy-permissions error.

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[benc]

STEPS:
Preferences | Advanced | Manual
Configure HTTP proxy to use proxy.

Create document.
Publish to HTTP URL.

EXPECTED:

Display error that proxy server returned.

OBSERVED:

Publishing to Site: <site>

Site URL: http://<site>/<path>/

Page subdirectory: <dir>/

Publishing Status:

Publishing failed.
The subdirectory "<dir>" doesn't exist on this site or the filename "<file>" is
already in use by anothe subdirectory.

x <file>

here's the proxy's access and error log entries:

<IP> - - [29/May/2003:12:49:34 -0700] "PUT <URL> HTTP/1.0" 403 182 - - 231 - 470
143 - - -

[29/May/2003:12:49:34] security: for host <IP> trying to PUT <URL>, acl-state
reports: access of <URL> denied by ACL <ACL> directive 1

Comment 1

[Robert Kaiser]

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

Comment 2

[Robert Kaiser]

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