1376067 - Caching 404 for site that is back online

Status: RESOLVED INCOMPLETE

(Core :: Networking: Cache, defect)

Description

[Emma Irwin]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20170618030207

Steps to reproduce:

1. My webpage: tiptoes.ca  was down with a 500 error. 
2.  The page not available/way back machine displayed. (expected)
3.  My server was rebooted and the page should have been back 
4.  Way back machine / 404 still showed.
5. In chrome tiptoes.ca is rendered .


Actual results:

for whatever reason, caching, my site still shows as being down in firefox, when it's not.


Expected results:

tiptoes.ca should have shown the live site not the 404 / way back machine

Comment 1

[Mark Nottingham]

Do you have a copy of the 500 error that was sent (with headers)?

Comment 2

[Honza Bambas (:mayhemer)]

Yes, that would be the interesting part - you can find it e.g. in about:cache.  Please, also backup the cache2/entries from the local part of the profile if you can (the HTTP cache content) so that we don't loose the cached data to diagnoses.

If you still can reproduce, you can also prove a log: https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Comment 3

[Emma Irwin]

here's what the console currently says:

Host: tiptoes.ca
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:56.0) Gecko/20100101 Firefox/56.0
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
Accept-Language: en-US,en;q=0.5
Accept-Encoding: gzip, deflate
Cookie: wp-settings-1=editor%3Dtinymce%26imgsize%3Dfull%26hidetb%3D1%26align%3Dleft%26libraryContent%3Dbrowse%26urlbutton%3Dpost%26ed_size%3D352%26advImgDetails%3Dshow%26dfw_width%3D822%26post_dfw%3Doff; wp-settings-time-1=1497800651; sc_is_visitor_unique=rx8043554.1497806466.43D5074879824FD232597EB908E5C838.56.51.48.47.44.40.33.31.23-10584380.1494433539.1.1.1.1.1.1.1.1.1; PHPSESSID=6ca166fda3644f9550c5d601f66835f1; wordpress_test_cookie=WP+Cookie+check; wordpress_logged_in_af6459b1e8147e15c2241a24d0ee74f1=eirwin%7C1497973295%7CZFqIqSwjxMZqMnyUxnvFw0msKfIwuP9ehXI7WEJCdFp%7C4e83312832e39faff45ff9e1001787241cf091ba811b9e0812fae088de67278a
Connection: keep-alive
Upgrade-Insecure-Requests: 1

Server: nginx/1.10.1
Date: Tue, 27 Jun 2017 01:04:50 GMT
Content-Type: text/html
Content-Length: 0
Connection: keep-alive
X-Frame-Options: SAMEORIGIN
Accept-Ranges: bytes

Comment 4

[Honza Bambas (:mayhemer)]

(In reply to Emma Irwin from comment #3)
> here's what the console currently says:
> 
> Host: tiptoes.ca
> User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:56.0)
> Gecko/20100101 Firefox/56.0
> Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8
> Accept-Language: en-US,en;q=0.5
> Accept-Encoding: gzip, deflate
> Cookie:
> wp-settings-
> 1=editor%3Dtinymce%26imgsize%3Dfull%26hidetb%3D1%26align%3Dleft%26libraryCont
> ent%3Dbrowse%26urlbutton%3Dpost%26ed_size%3D352%26advImgDetails%3Dshow%26dfw_
> width%3D822%26post_dfw%3Doff; wp-settings-time-1=1497800651;
> sc_is_visitor_unique=rx8043554.1497806466.43D5074879824FD232597EB908E5C838.
> 56.51.48.47.44.40.33.31.23-10584380.1494433539.1.1.1.1.1.1.1.1.1;
> PHPSESSID=6ca166fda3644f9550c5d601f66835f1;
> wordpress_test_cookie=WP+Cookie+check;
> wordpress_logged_in_af6459b1e8147e15c2241a24d0ee74f1=eirwin%7C1497973295%7CZF
> qIqSwjxMZqMnyUxnvFw0msKfIwuP9ehXI7WEJCdFp%7C4e83312832e39faff45ff9e1001787241
> cf091ba811b9e0812fae088de67278a
> Connection: keep-alive
> Upgrade-Insecure-Requests: 1
> 
> Server: nginx/1.10.1
> Date: Tue, 27 Jun 2017 01:04:50 GMT
> Content-Type: text/html
> Content-Length: 0
> Connection: keep-alive
> X-Frame-Options: SAMEORIGIN
> Accept-Ranges: bytes

Is this the 404 or 500 or which response?  I'm confused.  The Date header suggests it's been generated on 27 Jun by the server, not on 24 Jun as this bug has been reported.

Still, an HTTP log would be a good thing to collect, if you can.  See again comment 2.

Comment 5

[Emma Irwin]

I provided this as per about:cache directions.

It was a 500 error, but the Firefox 404 way back machine is displayed, and continues to display even when the site is online. 
This was in the console for the 27th, with 404 still displaying. 
It's back and up and working now, I did make a copy of the cache, but haven't had time to go through it to find exact date. Maybe if this one doesn't help, close for now.  Thanks

Comment 6

[Honza Bambas (:mayhemer)]

(In reply to Emma Irwin from comment #5)
> I provided this as per about:cache directions.
> 
> It was a 500 error, but the Firefox 404 way back machine is displayed, and
> continues to display even when the site is online. 
> This was in the console for the 27th, with 404 still displaying. 
> It's back and up and working now, I did make a copy of the cache, but
> haven't had time to go through it to find exact date. Maybe if this one
> doesn't help, close for now.  Thanks

If you still can reproduce it by copying the cache2/entries backup back, please provide a log then according https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging

Please also restate which URL is the one in question here so I can more easily locate it.  Thanks.

Comment 7

[Honza Bambas (:mayhemer)]

Closing for lack of data.