HEAD request responses (403,405) and user customizability

[GoogleCodeExporter]

User reported a website with valid HTTPS, but detection wasn't working.  The 
response to the initial HTTPS HEAD request was 403.  Currently (v0.34 and 0.44) 
we send a head request, and if we get a 405 response we try again with GET.  My 
temporary fix was to do "if response = 405 OR 403, retry with GET".  

A way to expand on this would be to add an 'Advanced" preference window with 
two choices for detection:

 - Default to GET (Possibly slower, but more reliable)
 - Default to HEAD, fall back to GET (Faster most of the time, but may miss certain sites)

People with fast connections may prefer to default GET, whereas on my DSL 
connection it seems noticeably quicker using HEAD (except for those rare few 
that fall back to get, in which case it takes twice as long).  

Original issue reported on code.google.com by jacobsK...@gmail.com on 13 Apr 2011 at 4:51

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

[deleted comment]

[GoogleCodeExporter]

Original comment by jacobsK...@gmail.com on 14 Apr 2011 at 1:46

• Changed state: Started

[GoogleCodeExporter]

Advanced menu added in 0.46 - user can select GET only, or HEAD (falling back 
to GET).

Original comment by jacobsK...@gmail.com on 16 Apr 2011 at 1:45

[GoogleCodeExporter]

Fixed and released in 0.50

Original comment by jacobsK...@gmail.com on 23 Apr 2011 at 6:12

• Changed state: Verified