Tom,
Create a view that accepts a "uri" argument and returns a 302 to the provided
URI. Then, update your redirect_to callable to urlencode the URI and send them
to /your/redirect/view/?uri=[encoded URI] and problem solved.
--
You received this message because you are subscribed to the Google
Hi,
On Tuesday, December 11, 2012 11:31:17 AM UTC+1, Tom Evans wrote:
>
> Is the second part of the fix in any way optional?
>
Nope, there is no way to disable that behavior currently.
Cheers,
Florian
--
You received this message because you are subscribed to the Google Groups
"Django develo
On Mon, Dec 10, 2012 at 10:38 PM, James Bennett wrote:
> Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued
> in response to security issues.
>
> Details are available here:
>
> https://www.djangoproject.com/weblog/2012/dec/10/security/
>
Is the second part of the fix in any w
Yeah, we know -- we usually wait a bit (24 hours, give or take) before we
tag them. Thanks for the spot.
Jacob
On Mon, Dec 10, 2012 at 11:09 PM, Yo-Yo Ma wrote:
> There aren't yet Git tags for the releases.
>
> --
> You received this message because you are subscribed to the Google Groups
> "D
There aren't yet Git tags for the releases.
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To view this discussion on the web visit
https://groups.google.com/d/msg/django-developers/-/ipPpizg3flcJ.
To post to this group, send email to dj
Django 1.3.5, Django 1.4.3 and Django 1.5 beta 2 have just been issued
in response to security issues.
Details are available here:
https://www.djangoproject.com/weblog/2012/dec/10/security/
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
