Closed Bug 203831 Opened 23 years ago Closed 23 years ago

Mozilla Calendar chokes on webserver response 304 when fetching calendar data

Categories

(Calendar :: General, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 203833

People

(Reporter: satmd, Assigned: mikeypotter)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.4a; MultiZilla v1.4.0.4A) Gecko/20030401 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; de-AT; rv:1.4a; MultiZilla v1.4.0.4A) Gecko/20030401 A messagebox pops up telling me that Moz Cal cannot download the data if the webserver sends a Status 304 (NOT MODIFIED) instead of the file (200). Reproducible: Always Steps to Reproduce: 1. Subscribe to any iCal that's located e.g. on a correctly configured Apache webserver 2. Fetch that iCal multiple times (while server content is not changing) 3. See this messagebox pop up Actual Results: Nothing. No updates were performed (which is correct after all as the iCal wasn't updated on the server, too) Expected Results: I expected this to work without that messagebox There are 2 possibilities to solve this: 1. Filter the 304 server-sideous and make it look 202 (I used two VirtualHosts. One is proxying the other with "NoCache *") [ I tried this and it works. Ugly solution.] 2. Just accept an status 304 as an successfull update. E.g.: Correct update: Moz Cal requests update -> Webserver sends file (200) -> update is imported Problem && solution : Before: Moz Cal requests update -> Webserver send Status 304 -> Moz Cal cannot cope with this -> Messagebox After: Moz Cal requests update -> Webserver send Status 304 -> Moz Cal sees this as an successful update -> normale operation will continue
*** This bug has been marked as a duplicate of 203833 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
The bugspam monkeys have been set free and are feeding on Calendar :: General. Be afraid for your sanity!
QA Contact: gurganbl → general
You need to log in before you can comment on or make changes to this bug.