Re: [Django] #9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string

[Django]

#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
+
 Reporter:  Malcolm Tredinnick  |Owner:  (none)
 Type:  Bug |   Status:  new
Component:  Core (Other)|  Version:  1.0
 Severity:  Normal  |   Resolution:
 Keywords:  | Triage Stage:  Accepted
Has patch:  1   |  Needs documentation:  0
  Needs tests:  0   |  Patch needs improvement:  1
Easy pickings:  0   |UI/UX:  0
+
Changes (by Tim Graham):

 * needs_better_patch:  0 => 1


--
Ticket URL: 
Django 
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.22ecdcf553f1eae4e83d224634ae24d7%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string

[Django]

#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
+
 Reporter:  Malcolm Tredinnick  |Owner:  (none)
 Type:  Bug |   Status:  new
Component:  Core (Other)|  Version:  1.0
 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 Tim Graham):

 * has_patch:  0 => 1


Comment:

 [https://github.com/django/django/pull/7663 PR]

--
Ticket URL: 
Django 
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.b78eb4612a543f6e20fc1f544ec3cc10%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string

[Django]

#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
--+
 Reporter:  mtredinnick   |Owner:
 Type:  Bug   |   Status:  new
Component:  Core (Other)  |  Version:  1.0
 Severity:  Normal|   Resolution:
 Keywords:| Triage Stage:  Accepted
Has patch:  0 |  Needs documentation:  0
  Needs tests:  0 |  Patch needs improvement:  0
Easy pickings:  0 |UI/UX:  0
--+

Comment (by timgraham):

 A [https://github.com/django/django/pull/6978 PR] with some discussion of
 this issue.

--
Ticket URL: 
Django 
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.0a40e30a4591bd2c3e9974ad4063b285%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.

Re: [Django] #9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string

[Django]

#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
-+--
  Reporter:  mtredinnick | Owner:  mtredinnick
Status:  assigned| Milestone: 
 Component:  Core framework  |   Version:  1.0
Resolution:  |  Keywords: 
 Stage:  Unreviewed  | Has_patch:  0  
Needs_docs:  0   |   Needs_tests:  0  
Needs_better_patch:  0   |  
-+--
Changes (by mtredinnick):

  * owner:  nobody => mtredinnick
  * needs_better_patch:  => 0
  * status:  new => assigned
  * needs_tests:  => 0
  * needs_docs:  => 0

Comment:

 I want to make sure we at least look at this. It may or may not be an
 actual issue, since Django's URL resolver doesn't care about the leading
 '/'; it just treats it as a separator and there must be some kind of
 "first character" in the URL. So I suspect it's probably not actually
 causing any misbehaviour and we're just ensuring the `PATH_INFO`
 equivalent is in a reasonably normalised form. However, we should make
 sure that the reported information (via `request.path_info`) matches
 reality, which may be an empty string, so that means differentiating
 between our internal normalised version and the upstream passed-in
 version.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---

[Django] #9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string

[Django]

#9435: Check out behaviour of wsgi backend with PATH_INFO being an empty string
+---
 Reporter:  mtredinnick |   Owner:  nobody
   Status:  new |   Milestone:
Component:  Core framework  | Version:  1.0   
 Keywords:  |   Stage:  Unreviewed
Has_patch:  0   |  
+---
 Transferring a side-issue from #3414 (comment 23 over there):

 Note: the WSGI spec allows PATH_INFO to be empty or missing; specifically:

 "This may be an empty string, if the request URL targets the application
 root and does NOT have a trailing slash." (emph. added)

 And WSGI servers are allowed to omit PATH_INFO (and various other
 variables) if they are an empty string.

 IIUC, this means that [8105] doesn't correctly handle the case where
 someone goes to "foo.com/django" (no trailing '/'), because it wrongly
 assumes that a missing PATH_INFO is a '/'. Per the WSGI spec, a missing
 PATH_INFO is in fact an empty string. That means that relative URLs at the
 root of a Django site would not work correctly under servers that omit an
 empty PATH_INFO.

 Whether the OP issue here is a configuration problem is irrelevant to this
 piece: it is perfectly legal for a WSGI server to omit PATH_INFO if it's
 an empty string, and its omission means that it's an EMPTY string, not a
 '/'.

 Conversely, if a WSGI server is ommitting PATH_INFO when PATH_INFO should
 be a "/" (i.e. the URL was "foo.com/django/" with a trailing "/"), then
 that server is seriously broken and should be fixed. (But I'm not seeing
 anything here that suggests this is actually the case.)

 Either way, however, the code that's defaulting a missing PATH_INFO to "/"
 appears to be quite wrong: either creating a bug or masking one somewhere
 else.

-- 
Ticket URL: 
Django 
The Web framework for perfectionists with deadlines.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups 
"Django updates" group.
To post to this group, send email to django-updates@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-updates?hl=en
-~--~~~~--~~--~--~---