On 8/5/07, James Bennett <[EMAIL PROTECTED]> wrote:
> I'm almost certain it has to do with a combination of the regular
> expression patterns for the URLs (minor contribution) and the database
> collation in use (major contribution). Which, again, means that it's
> not something Django is necessar
On 8/5/07, Brett Hoerner <[EMAIL PROTECTED]> wrote:
> Not on our live site. And I just made a fresh django-trunk project to
> test it, didn't work there either. Although aren't resolvers just
> normal Python REs, so you could possibly have set this for yourself
> somehow?
I'm almost certain it
On 8/5/07, James Bennett <[EMAIL PROTECTED]> wrote:
> Django handles both just fine, returns the same page for both.
Not on our live site. And I just made a fresh django-trunk project to
test it, didn't work there either. Although aren't resolvers just
normal Python REs, so you could possibly h
Finger slipped on the "send" shortcut, continuing where I left off...
On 8/5/07, James Bennett <[EMAIL PROTECTED]> wrote:
> And again, I'll reiterate that the type of user who doesn't understand
> case-sensitivity is the type of user who -- verified by repeated
> real-world usability testing -- f
On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
> Imagine that your site hosting photos has got the following urls
> belonging to different users:
> http://mysite.com/John/
> http://mysite.com/john.
Except those aren't different URLs. And now that I'm slightly more
awake I'm wondering why
You wrote 5 ??? 2007 ?., 17:15:11:
> On 8/5/07, Alex Nikolaenkov <[EMAIL PROTECTED]> wrote:
>>The urls are pretty same. But the second one causes 404 Response.
>>While typing the second url the user tries to access typing its
>>address and types "Simpsons" instead of "simpsons". I
