1256656 - FeedFetcher: Research ETag behavior

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Sebastian Kaspari (:sebastian; :pocmo)]

From bug 1241810:

> https://reviewboard.mozilla.org/r/36459/#review35481
> 
> > Why do we remove the weak indicator? I'd assume the server would want the identical etag back.
> 
> In my tests the server always returned the full content (HTTP 200) if I send
> the ETag including weak indicator. Only after stripping the weak indicator
> and just sending the ETag I got 304 Not Modified.
> 
> Compare:
> http -p hH https://googleblog.blogspot.de/atom.xml
> http -p hH https://googleblog.blogspot.de/atom.xml
> If-None-Match:W/"b74c6093-3602-4de1-b935-9bd274b56db4"   (Replace with the
> current Etag)
> http -p hH https://googleblog.blogspot.de/atom.xml
> If-None-Match:"b74c6093-3602-4de1-b935-9bd274b56db4"
> 
> RFC 7232 ETag
> https://tools.ietf.org/html/rfc7232#section-2.3
> 
> RFC 7232 If-None-Match
> https://tools.ietf.org/html/rfc7232#section-3.2
> 
> From the RFCs I also assume that we should send the weak indicator - but
> this is not what blogspot (The only whitelisted service that sends ETags)
> understands. Looking at the RFC it looks like it would be safe to just send
> both "If-None-Match: weak, without" but it looks like blogspot doesn't
> understand this either.
> 
> Also see RFC 2616:
> https://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html#sec13.3.3
> 
> My understanding is that you are right: We should not strip the indicator
> but it seems like blogspot is behaving differently (or am I doing something
> wrong here?). It's worth exploring this is a follow-up bug further.
> Especially if we add more services that may have conflicting ETag validators.

Comment 1

[Sebastian Kaspari (:sebastian; :pocmo)]

This code is gone.