200839 - unknown publishing error occurred when publishing on NT4 server (http put)

Status: RESOLVED EXPIRED

(SeaMonkey :: Composer, defect)

Description

[Ceriel Jacobs]

User-Agent:       Opera/7.03 (Windows NT 5.0; U)  [en]
Build Identifier: 1.4a

When publishing from composer to a Windows NT4 server, the publishing proces 
fils with an "Unknow publishing error occured".


- Tested both publishing and publish as: both fail


- Tested both with and without user password security: both fail


- Tested publishing only the page and page with all referenced files: both fail, 
althoug when publishing with referenced files to the same directory, one file 
gets uploaded correctly, one fails, and one file is forgotten


- Tested with Mozilla 1.2.1: runs without any problem (1 html file and three 
images are correctly uploaded).




See this server log for a publish with user password security and all related 
files included:


1. first a correct publish is done with Mozilla 1.2.1. 


2. than a publish is done with Mozilla 1.4a


---


20:14:37 217.120.106.177 hemelrijk PUT /e-mailing/Helikopter.gif - 200 356 3464 
Mozilla/5.0+(Windows;+U;+Windows+NT+5.0;+en-US;+rv:1.2.1)+Gecko/20021130 -


20:14:37 217.120.106.177 hemelrijk PUT /e-mailing/Handtekening_Billy_Bird.gif - 
200 369 1816 Mozilla/5.0+(Windows;+U;+Windows+NT+5.0;+en-US;+rv:1.2.1)
+Gecko/20021130 -


20:14:40 217.120.106.177 hemelrijk PUT /e-mailing/jongetjes_Helihaven6.JPG - 200 
366 17956 Mozilla/5.0+(Windows;+U;+Windows+NT+5.0;+en-US;+rv:1.2.1)
+Gecko/20021130 -


20:14:40 217.120.106.177 hemelrijk PUT 
/e-mailing/2003_04_20_Opening_Helihaven_Hemelrijk.html - 200 386 5947 Mozilla/5.
0+(Windows;+U;+Windows+NT+5.0;+en-US;+rv:1.2.1)+Gecko/20021130 -


20:15:19 217.120.106.177 - PUT /e-mailing/Helikopter.gif - 401 789 511 
Mozilla/5.0+(Windows;+U;+Windows+NT+5.0;+en-US;+rv:1.4a)+Gecko/20030401 -


20:15:19 217.120.106.177 hemelrijk PUT /e-mailing/Helikopter.gif - 200 356 3429 
Mozilla/5.0+(Windows;+U;+Windows+NT+5.0;+en-US;+rv:1.4a)+Gecko/20030401 -


---


Reproducible: Always

Steps to Reproduce:
1.


2.


3.

Comment 1

[Kathleen :Brade]

Darin--is this a duplicate of the other bug you have with a fix already?

Comment 2

[Kathleen :Brade]

Ceriel Jacobs--can you test this on a newer mozilla build and see if it has been
fixed?

Comment 3

[Ceriel Jacobs]

The latest nightly build partly fixes the problem:




1. The PUT proces succeeds


08:22:06 x.x.x.x liisa-art PUT /what2.html - 200 234 11306 Mozilla/5.0+(Windows;
+U;+Windows+NT+5.0;+en-US;+rv:1.4b)+Gecko/20030425 -




2. The user interface although displays that publishing fails.


"Publishing failed: unknown publishing error occured". 

Comment 4

[Kathleen :Brade]

-->jag for investigation on why the error message shows up

Comment 5

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

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