356534 - Publishing to FTP fails when using automatic proxy configuration

Status: RESOLVED WORKSFORME

(Calendar :: General, defect)

Description

[Raj Bhaskar]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061002 MultiZilla/1.8.3.0a SeaMonkey/1.5a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20061002 MultiZilla/1.8.3.0a SeaMonkey/1.5a

I upgraded from Sunbird 0.2 to 0.3, nuked my profile, saved my local ics file and started from scratch.  I was able to import the ics file from 0.2 successfully and subscribe to a Google Calendar that I watch.

However, I want to be able to share my work calendar between work and home, which I do by publishing it to my personal FTP server whenever I update it and subscribing to it from home.

I right-clicked on the calendar as I did before, selected "Publish Calendar..." and got the expected dialog box.  I entered the URL in the form:

ftp://[e-mail]/path/to/file.ics

Expecting that I would be asked for my password by the password manager, as 0.2 did.  However, nothing happens, and I get the following error repeated three times in the Error Console:

Error: [Exception... "Component returned failure code: 0x80004002 (NS_NOINTERFACE) [nsISupports.QueryInterface]"  nsresult: "0x80004002 (NS_NOINTERFACE)"  location: "JS frame :: chrome://calendar/content/publish.js :: publishItemArray :: line 176"  data: no]
Source File: chrome://calendar/content/publish.js
Line: 176

Reproducible: Always

Steps to Reproduce:
1. Right-click a local calendar and select "Publish Calendar..."
2. In the resulting dialog box, enter an FTP URL including a username
3. Click Publish

Actual Results:  
Calendar is not published and the error noted above appears in the Error console

Expected Results:  
Calendar should be published to an ICS file on the server.

Comment 1

[Raj Bhaskar]

Further testing reveals that this only happens when using Automatic Proxy Configuration.  If I set it to Manual (to workaround bug 338527) then the FTP upload succeeds.

Comment 2

[Bas van den Bosch]

So this is the same issue as bug 338527 I assume? 

Comment 4

[Martin Schröder [:mschroeder]]

Philipp, I'm not sure this issue (publishing & proxy) has been fixed with the patch from bug 338527. Please, can you have a look?

-> Reopening

Comment 5

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

I've tested this, it works for me