Re: Capturing full URL string

2008-06-05 Thread John M
Ticket 7379 http://code.djangoproject.com/ticket/7379 On Jun 5, 2:41 pm, John M <[EMAIL PROTECTED]> wrote: > How exciting, im actually getting involved (via Karen of course), > I'll submit today and put the ticket number back here. > > Thanks so much. > > John > > On Jun 5, 10:28 am, "Karen

Re: Capturing full URL string

2008-06-05 Thread John M
How exciting, im actually getting involved (via Karen of course), I'll submit today and put the ticket number back here. Thanks so much. John On Jun 5, 10:28 am, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Wed, Jun 4, 2008 at 4:35 PM, John M <[EMAIL PROTECTED]> wrote: > > > Well, thank

Re: Capturing full URL string

2008-06-05 Thread Karen Tracey
On Wed, Jun 4, 2008 at 4:35 PM, John M <[EMAIL PROTECTED]> wrote: > > Well, thank God you took a look at the code and agreed on my > findings. I'll just adjust my urls.py for now. > > Should I submit a bug report? (it'd be my first :) ) > > Thanks again for your time on this, I'm glad it was a b

Re: Capturing full URL string

2008-06-05 Thread Leeland (The Code Janitor)
I read this with great interest. It actually will save me time on my project. I will be encountering this behavior shortly. Thank you! Please, please submit a bug report on this with all the details here. If people do not submit bug reports future user of Django will eventually have the same prob

Re: Capturing full URL string

2008-06-04 Thread John M
Well, thank God you took a look at the code and agreed on my findings. I'll just adjust my urls.py for now. Should I submit a bug report? (it'd be my first :) ) Thanks again for your time on this, I'm glad it was a bug and not my mis-standing of django or the way this all works together. Now

Re: Capturing full URL string

2008-06-04 Thread Karen Tracey
On Wed, Jun 4, 2008 at 2:03 PM, John M <[EMAIL PROTECTED]> wrote: > Yes, I understand that, and I think it's a good thing, but when it > redirects, it mangles the parameters, would you agree? > Yes, I think that's a bug in Django. The code that is doing the APPEND_SLASH handling tries to use req

Re: Capturing full URL string

2008-06-04 Thread John M
Yes, I understand that, and I think it's a good thing, but when it redirects, it mangles the parameters, would you agree? J On Jun 4, 10:35 am, Gregor Müllegger <[EMAIL PROTECTED]> wrote: > This is because Django will redirect you to a page with an appended > slash to your url if it's not alread

Re: Capturing full URL string

2008-06-04 Thread Matthias Kestenholz
Hi, On Wed, 2008-06-04 at 09:30 -0700, John M wrote: > I am running into some weirdness in an app im writing and so I thought > I'd try to see how the basics of URL strings are handled. > > So I wrote a one line hello world app, and wanted to see how the dev > server output it's results. I am s

Re: Capturing full URL string

2008-06-04 Thread Gregor Müllegger
This is because Django will redirect you to a page with an appended slash to your url if it's not already there -- how you have discovered. To understand why this is done you should read the following section in django's documentation: http://www.djangoproject.com/documentation/middleware/#django

Re: Capturing full URL string

2008-06-04 Thread John M
Well, in investigating this further, I think I found the 'issue'. There are a few threads with similar issues, where the pattern in urls.py doesn't capture the trailing slash, and I guess by default, django figures it will 'adjust' the URL and redirect to the 'correct' URL, hence the initial 301,

Capturing full URL string

2008-06-04 Thread John M
I am running into some weirdness in an app im writing and so I thought I'd try to see how the basics of URL strings are handled. So I wrote a one line hello world app, and wanted to see how the dev server output it's results. I am still getting my feet wet with the whole web / http / HTML thing,