Closed Bug 1288274 Opened 8 years ago Closed 8 years ago

'safe' should be 'cacheable' in HTTP requests overview page

Categories

(Developer Documentation Graveyard :: Protocols, defect, P5)

Product:
Developer Documentation Graveyard
Component:
Protocols
Platform:
All
Other
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: davidsscales, Unassigned)

References

(
URL
)

Details

:: Developer Documentation Request

      Request Type: Correction
     Gecko Version: unspecified
 Technical Contact: 

:: Details

"e.g. a request method can be safe, idempotent, or safe" - there should not be two instances of "safe" here. I assume one should be "unsafe" and should link out appropriately.
David, good catch, it is obvious 'cacheable'.

We have started to (re)write and expand our HTTP documentation last Monday, so a lot of new text has not yet gone through our internal review process. Feedback is very welcome1
Status: UNCONFIRMED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Summary: Typo with incorrect link → 'safe' should be 'cacheable' in HTTP requests overview page
You need to log in before you can comment on or make changes to this bug.