Closed Bug 1558085 Opened 7 years ago Closed 6 years ago

When aws instances are replaced with the same IP address, firefox cache causes slow https response / hang

Categories

(Core :: Networking: Cache, defect)

67 Branch
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: connect, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:67.0) Gecko/20100101 Firefox/67.0

Steps to reproduce:

I use a softnas instance in aws that presents a ui via html (https). that instance may bve destroyed and recreated based on demand, and over time (perhaps after 7 or so instances) I wont be able to access the page at the same IP address unless I clear the firfox cache/cookies/settings

Actual results:

cannot access web page

Expected results:

I should be able to see the webpage without having to erase firefox settings / cache. as a side note safari does not have this issue.

After trying to obtain confirmation from the SoftNAS side, I got this recommendation: "Support recommends the customer to just turn off his caching. If the issue is that it's caching the IP over again. Then to resolve is to either turn caching off or to clear the cache."

Considering that their services aren't free and that credit card information is required to obtain a free trial account, I cannot confirm this issue. I will set its component to (Core) Networking: Cache and hope that someone there will have a more productive opinion on how to address this issue.

Please NI me if manual testing is needed, along with the required information. Thank you for your contribution!

Component: Untriaged → Networking: Cache
Product: Firefox → Core

Please provide a log (https://developer.mozilla.org/en-US/docs/Mozilla/Debugging/HTTP_logging) with a description which URL fails to load and how, i.e. whether load hangs or finishes with an empty or an error page.

Flags: needinfo?(connect)
Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.