Sorry the culprit that is escaping slashes is urlencode not django....
if you do urllib.parse.urlencode( {"next" : "/a/b/c"} ) is python3 you'll
see lots of %2F's in the output..
I want to get rid of those if that's not a problem
On Saturday, April 23, 2016 at 7:50:21 PM UTC-5, Stephen Butler wrote:
>
> You mean on the standard login form? The hidden "next" form value? That
> value isn't part of a URL so it isn't URL escaped. It's part of the HTML
> attribute value, so it is HTML attribute escaped.
>
> On Sat, Apr 23, 2016 at 6:19 PM, Chris Seberino <[email protected]
> <javascript:>> wrote:
>
>> But I still don't see why sometimes the slash is escaped then sometimes
>> it isn't. I've seen both ways for query parameters.... The ugly Escape
>> version shows up when I have handmade URLs but not when Django creates the
>> next URL itself like for logging in
>>
>> --
>> You received this message because you are subscribed to the Google Groups
>> "Django users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> To post to this group, send email to [email protected]
>> <javascript:>.
>> Visit this group at https://groups.google.com/group/django-users.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/django-users/4301c013-2b27-427b-8f0e-d7e13bc13112%40googlegroups.com
>> .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-users/90d0a35e-f8c7-4ccb-aa7e-ca51d89de7d4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
