Closed Bug 1479306 Opened 7 years ago Closed 7 years ago

Rapid timeout when editing documents

Categories

(developer.mozilla.org Graveyard :: Editing, enhancement, P3)

All
Other
enhancement

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: bhackett1024, Unassigned)

Details

(Keywords: in-triage, Whiteboard: [specification][type:bug][points:1])

What did you do? ================ 1. Make an edit to https://developer.mozilla.org/en-US/docs/Mozilla/Projects/WebReplay 2. Press 'Publish' What happened? ============== After a few seconds, a plain 'Request Timeout.' page appeared. What should have happened? ========================== The edit should have gone through. I am on a high latency connection and the timeout value seems too low. This makes it impossible for me to edit MDN documents. Is there anything else we should know? ======================================
I'm sorry you had trouble editing that page. I do see two 408 Request Timeouts for that page within 3 minutes of each other, but no other 408s that hour. There have been many successful edits in the last 24 hours. I suspect this was an intermittent issue, and it would work if you retried. Can you retry your edit?
Flags: needinfo?(bhackett1024)
Keywords: in-triage
Priority: -- → P3
Whiteboard: [specification][type:bug] → [specification][type:bug][points:1]
Hi, I just tried again and am still getting the 'Request Timeout.' message.
Flags: needinfo?(bhackett1024)
OK, I tried again and was able to update the page.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
rjohnson: Do we need a CDN rule to avoid caching 408 responses? That may explain why a temporary issue persisted for a few days.
Flags: needinfo?(rjohnson)
According to CloudFront docs, 408 is not one of the cached responses, or at least you can't customize the response: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/HTTPStatusCodes.html#HTTPStatusCodes-cached-errors
Flags: needinfo?(rjohnson)
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.