#24720: using middleware.common to append slashes causes extra overhead to all
requests that do not end in a slash
-------------------------------------+-------------------------------------
     Reporter:  electricjay          |                    Owner:  nobody
         Type:                       |                   Status:  closed
  Cleanup/optimization               |
    Component:  Core (Other)         |                  Version:  master
     Severity:  Normal               |               Resolution:  fixed
     Keywords:  optimization         |             Triage Stage:  Accepted
  middleware common                  |
    Has patch:  1                    |      Needs documentation:  1
  Needs tests:  0                    |  Patch needs improvement:  0
Easy pickings:  0                    |                    UI/UX:  0
-------------------------------------+-------------------------------------
Changes (by Tim Graham <timograham@…>):

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


Comment:

 In [changeset:"434d309ef6dbecbfd2b322d3a1da78aa5cb05fa8" 434d309e]:
 {{{
 #!CommitTicketReference repository=""
 revision="434d309ef6dbecbfd2b322d3a1da78aa5cb05fa8"
 Fixed #24720 -- Avoided resolving URLs that don't end in a slash twice in
 CommonMiddleware.

 This speeds up affected requests by about 5%.
 }}}

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

-- 
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to django-updates+unsubscr...@googlegroups.com.
To post to this group, send email to django-updates@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/django-updates/069.400e78592f866d30d89dcf4e613ccc3b%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to