908715 - When receiving a 410 Gone, do not try again to request the calendar

Status: RESOLVED FIXED

(Calendar :: Lightning Only, defect)

Description

[Karl Dubost💡 :karlcow]

0. Someone subscribe to a calendar (which exists or not)
1. At a point in time, HTTP request generates a "410 Gone" response from the server
2. The client MUST NOT send another HTTP request to this resource


This is an example for the last two days.
I removed the IP addresses for privacy reasons

 82 *.*.*.* "Mozilla/5.0 (Windows NT 6.0; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 Lightning/1.9.1"
 82 *.*.*.* "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130625 Thunderbird/17.0.7 Lightning/1.9.1"
 82 *.*.*.* "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 Lightning/1.9.1"
 81 *.*.*.* "Mozilla/5.0 Mnenhy/0.7.6.666 Lightning/1.2b1"
 61 *.*.*.* "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130809 Thunderbird/17.0.7 Lightning/1.9b1"
 58 *.*.*.* "Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 Lightning/1.9.1"
 37 *.*.*.* "Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 Lightning/1.9.1"
 33 *.*.*.* "Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:12.0) Gecko/20120428 Thunderbird/12.0.1 Lightning/1.4"
 23 *.*.*.* "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 Lightning/1.9.1"
 23 *.*.*.* "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130801 Thunderbird/17.0.8 Lightning/1.9.1"
 21 *.*.*.* "Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130416 Thunderbird/17.0.5 Lightning/1.9b1"
 20 *.*.*.* "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130809 Thunderbird/17.0.7 Lightning/1.9b1"
 18 *.*.*.* "Mozilla/5.0 (X11; Linux i686; rv:17.0) Gecko/20130416 Thunderbird/17.0.5 Lightning/1.9b1"
 16 *.*.*.* "Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130806 Thunderbird/17.0.8 Lightning/1.9.1"
 13 *.*.*.* "Mozilla/5.0 (Windows NT 5.1; rv:17.0) Gecko/20130801 

Thanks.

Comment 1

[Stefan Sitter [:ssitter]]

What calendar provider do you use? 

For CalDAV provider this seems fixed with Bug 874654. Maybe you could test with Thunderbird 24 Beta + Lightning 2.6 Beta?

For ICS provider there is a similar report in Bug 901450. The proposed patch is only for status 503 but maybe it should be more general like in Bug 874654.

Comment 2

[Karl Dubost💡 :karlcow]

I'm not using any CalDAV provider. It was an ics file on my own site, which is the most requested resource of my Web site. :) Interesting to detect the bogus products.

The context of the bug is 
http://lists.w3.org/Archives/Public/www-archive/2013Aug/0021.html

There is a combination of status and cache information that should change the behavior of the software (automatically or through user notification).

Comment 3

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

This will be fixed for the ICS provider in bug 901450.

Comment 4

[Karl Dubost💡 :karlcow]

This is not a duplicate. The Bug 901450 is about errors of category 5** in HTTP.
This one is about 410 Gone, aka the resource is Gone. A choice made by the provider to indicate that the resource is not available anymore. Errors 5** in HTTP are mistakes that the server doesn't know what happened. You may want to fetch the resource later. 4** in HTTP are servers saying that the client is wrong and should change its behavior for this resource. And for 410, It should say to the users something along "This resource has been terminated by the owner. We will not request it anymore. Confirm to delete it from your sources."

Comment 5

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

Yes, but the patch I uploaded in that bug handles the 410 case specially. It disables the calendar and doesn't auto-enable it on restart. This doesn't tell the user specifically why its failing I admit, but it will make the user try to figure out why.

Comment 6

[Martin Schröder [:mschroeder]]

This should be fixed in Lightning 3.2 by patch for bug 901450.