The problem is it looks bad! It makes the URL unreadable, which is what I want to prevent. For example, last.fm uses '+' symbols to separate band names.
http://www.last.fm/music/Goo+Goo+Dolls pretty obviously takes you to the page for the band "Goo Goo Dolls". http://www.last.fm/music/Goo%2BGoo%2BDolls, however, is far tougher to pick apart by a human reader. My short answer is I want to keep my URLs human readable. On Sep 12, 1:14 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > On Fri, Sep 12, 2008 at 1:49 PM, Ross <[EMAIL PROTECTED]> wrote: > > > Karen, you were exactly right: APPEND_SLASH is the culprit here. If > > you hit '/search/hotel+air/', the address stays that way. Hitting '/ > > search/hotel+air' though redirects you to '/search/hotel%2Bair/' > > > I am using '+' because it logically makes sense for what I am trying > > to do. I am doing a travel search, and for packages it would be > > something like '/search/hotel+air/'. You can append any number of > > travel pieces in there like '/search/cruise+hotel+car+air/'. The order > > of the pieces doesn't matter, because I split them on '+' when it gets > > to the view. > > > Even if '+' is meant to be a space in URL-speak, it conveys the right > > meaning for what I am trying to do. Is it possible to prevent > > APPEND_SLASH from percent encoding URLs? > > You didn't answer the part about why the percent-encoding is a problem? By > the time it gets to your view, the percent-encoding will be undone and your > view code can deal with '+' chars. (At least, that is how a quickly > modified view of my own sees it...sorry but I do not have time for a more > in-depth investigation at the moment). So, why is the percent-encoding done > by the redirect a problem? It should not be a problem so I'm having trouble > understanding why you want to prevent it. > > Karen > > > > > On Sep 12, 12:08 pm, "Karen Tracey" <[EMAIL PROTECTED]> wrote: > > > On Fri, Sep 12, 2008 at 12:31 PM, Ross <[EMAIL PROTECTED]> wrote: > > > > > Sorry, Julian, I misunderstood what you wrote. I see the Django HTML > > > > escaping doesn't change the '+' symbol, which makes this even more > > > > confusing... Even more strangely, this only happens intermittently. > > > > I'd guess this is only happening when you are, in fact, getting > > redirected > > > via APPEND_SLASH or something like that. No part of a normal response > > tells > > > the browser what to put in the address bar, so I don't see how anything > > done > > > by render_to_response could be involved here. > > > > What, exactly, is the problem with having the + percent-encoded in the > > URL? > > > Is it that it might be confusing to users or is there an actual failure > > to > > > route urls correctly once this has happened? > > > > Karen --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/django-users?hl=en -~----------~----~----~----~------~----~------~--~---
