[Django] #26567: Update references to the HTTP spec in the docs

4 views
Skip to first unread message

Django

unread,
May 2, 2016, 7:40:38 AM5/2/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec in the docs
--------------------------------------+--------------------
Reporter: vfaronov | Owner: nobody
Type: Cleanup/optimization | Status: new
Component: Documentation | Version: master
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Easy pickings: 0 | UI/UX: 0
--------------------------------------+--------------------
In multiple places, the docs reference
[https://tools.ietf.org/html/rfc2616 RFC 2616], which has been obsoleted
by RFCs [https://tools.ietf.org/html/rfc7230 7230] through
[https://tools.ietf.org/html/rfc7235 7235].

--
Ticket URL: <https://code.djangoproject.com/ticket/26567>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

Django

unread,
May 2, 2016, 7:42:03 AM5/2/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec
-------------------------------------+-------------------------------------
Reporter: vfaronov | Owner: nobody
Type: | Status: new
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by vfaronov):

* needs_better_patch: => 0
* needs_docs: => 0
* needs_tests: => 0


Old description:

> In multiple places, the docs reference
> [https://tools.ietf.org/html/rfc2616 RFC 2616], which has been obsoleted
> by RFCs [https://tools.ietf.org/html/rfc7230 7230] through
> [https://tools.ietf.org/html/rfc7235 7235].

New description:

In multiple places, the docs and code comments reference


[https://tools.ietf.org/html/rfc2616 RFC 2616], which has been obsoleted
by RFCs [https://tools.ietf.org/html/rfc7230 7230] through
[https://tools.ietf.org/html/rfc7235 7235].

--

--
Ticket URL: <https://code.djangoproject.com/ticket/26567#comment:1>

Django

unread,
May 2, 2016, 8:46:28 AM5/2/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec
-------------------------------------+-------------------------------------
Reporter: vfaronov | Owner: vfaronov
Type: | Status: assigned
Cleanup/optimization |
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed

Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by vfaronov):

* status: new => assigned
* owner: nobody => vfaronov


Comment:

Fixed it on my [https://github.com/vfaronov/django/tree/ticket_26567
vfaronov:ticket_26567] branch. Didn’t touch comments where it was not
obvious that the code adhered to the newer standard.

--
Ticket URL: <https://code.djangoproject.com/ticket/26567#comment:2>

Django

unread,
May 2, 2016, 10:21:22 AM5/2/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec
--------------------------------------+------------------------------------
Reporter: vfaronov | Owner: vfaronov
Type: Cleanup/optimization | Status: assigned
Component: Documentation | Version: master
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by timgraham):

* has_patch: 0 => 1
* stage: Unreviewed => Accepted


--
Ticket URL: <https://code.djangoproject.com/ticket/26567#comment:3>

Django

unread,
May 3, 2016, 11:16:01 AM5/3/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec
--------------------------------------+------------------------------------
Reporter: vfaronov | Owner: vfaronov
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master
Severity: Normal | Resolution: fixed

Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------
Changes (by Tim Graham <timograham@…>):

* status: assigned => closed
* resolution: => fixed


Comment:

In [changeset:"ac77c55bc5fc54cd763a7ae426784650a8cc97c9" ac77c55]:
{{{
#!CommitTicketReference repository=""
revision="ac77c55bc5fc54cd763a7ae426784650a8cc97c9"
Fixed #26567 -- Updated references to obsolete RFC2616.

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

--
Ticket URL: <https://code.djangoproject.com/ticket/26567#comment:4>

Django

unread,
May 3, 2016, 11:19:35 AM5/3/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec
--------------------------------------+------------------------------------
Reporter: vfaronov | Owner: vfaronov
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master

Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------

Comment (by Tim Graham <timograham@…>):

In [changeset:"cb33e553ee537da4915f9055f8cdf9bf32113aed" cb33e553]:
{{{
#!CommitTicketReference repository=""
revision="cb33e553ee537da4915f9055f8cdf9bf32113aed"
[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
}}}

--
Ticket URL: <https://code.djangoproject.com/ticket/26567#comment:5>

Django

unread,
May 3, 2016, 12:52:29 PM5/3/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec
--------------------------------------+------------------------------------
Reporter: vfaronov | Owner: vfaronov
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master

Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------

Comment (by claudep):

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

--
Ticket URL: <https://code.djangoproject.com/ticket/26567#comment:6>

Django

unread,
May 4, 2016, 6:52:31 AM5/4/16
to django-...@googlegroups.com
#26567: Update references to the HTTP spec
--------------------------------------+------------------------------------
Reporter: vfaronov | Owner: vfaronov
Type: Cleanup/optimization | Status: closed
Component: Documentation | Version: master

Severity: Normal | Resolution: fixed
Keywords: | Triage Stage: Accepted
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0

Easy pickings: 0 | UI/UX: 0
--------------------------------------+------------------------------------

Comment (by vfaronov):

Replying to [comment:6 claudep]:


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

Sure. #26580.

--
Ticket URL: <https://code.djangoproject.com/ticket/26567#comment:7>

Reply all
Reply to author
Forward
0 new messages