Opened 10 years ago

Closed 10 years ago

Last modified 10 years ago

#26567 closed Cleanup/optimization (fixed)

Update references to the HTTP spec

Reported by: Vasiliy Faronov Owned by: Vasiliy Faronov
Component: Documentation Version: dev
Severity: Normal Keywords:
Cc: Triage Stage: Accepted
Has patch: yes Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description (last modified by Vasiliy Faronov)

In multiple places, the docs and code comments reference ​RFC 2616, which has been obsoleted by RFCs ​7230 through ​7235.

Change History (7)

comment:1 by Vasiliy Faronov, 10 years ago

Description: modified (diff)
Summary: Update references to the HTTP spec in the docs → Update references to the HTTP spec

comment:2 by Vasiliy Faronov, 10 years ago

Owner: changed from nobody to Vasiliy Faronov
Status: new → assigned

Fixed it on my ​vfaronov:ticket_26567 branch. Didn’t touch comments where it was not obvious that the code adhered to the newer standard.

Version 0, edited 10 years ago by Vasiliy Faronov (next)

comment:3 by Tim Graham, 10 years ago

Has patch: set
Triage Stage: Unreviewed → Accepted

comment:4 by Tim Graham <timograham@…>, 10 years ago

Resolution: → fixed
Status: assigned → closed

In ac77c55:

Fixed #26567 -- Updated references to obsolete RFC2616.

Didn't touch comments where it wasn't obvious that the code adhered to
the newer standard.

comment:5 by Tim Graham <timograham@…>, 10 years ago

In cb33e553:

[1.9.x] Fixed #26567 -- Updated references to obsolete RFC2616.

Didn't touch comments where it wasn't obvious that the code adhered to
the newer standard.

Backport of ac77c55bc5fc54cd763a7ae426784650a8cc97c9 from master

comment:6 by Claude Paroz, 10 years ago

I think the same could be done with RFC 5322 replacing RFC 2822. vfaronov, up to a similar patch?

in reply to:  6 comment:7 by Vasiliy Faronov, 10 years ago

Replying to claudep:

I think the same could be done with RFC 5322 replacing RFC 2822. vfaronov, up to a similar patch?

Sure. #26580.

Note: See TracTickets for help on using tickets.
Back to Top