This was reported way back in the triple-digit days:
http://code.djangoproject.com/ticket/987
I took a couple of stabs at it a while ago. I patched
HttpResponseRedirect to prepend the domain to the current site
specified by settings.SITE_ID, as long as it's not the default
"example.com" (anyone
On Sun, 2007-04-08 at 12:52 +0200, Matias Hermanrud Fjeld wrote:
> Adrian Holovaty wrote:
> > On 4/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> >
> >> We currently have a bug in HttpResponseRedirect: the HTTP spec requires
> >> using absolutely URLs in the Location header for redirects
Adrian Holovaty wrote:
> On 4/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
>
>> We currently have a bug in HttpResponseRedirect: the HTTP spec requires
>> using absolutely URLs in the Location header for redirects.
>>
>
> This is a tricky one... Ideally, HttpResponseRedirect would a
On 4/6/07, Malcolm Tredinnick <[EMAIL PROTECTED]> wrote:
> We currently have a bug in HttpResponseRedirect: the HTTP spec requires
> using absolutely URLs in the Location header for redirects.
This is a tricky one... Ideally, HttpResponseRedirect would accept
relative URLs, handling the absolute-
Apropos of nothing in particular...
On Fri, 2007-04-06 at 21:26 -0500, [EMAIL PROTECTED] wrote:
> Author: adrian
> Date: 2007-04-06 21:26:45 -0500 (Fri, 06 Apr 2007)
> New Revision: 4941
>
> Modified:
>django/branches/newforms-admin/django/contrib/admin/options.py
> Log:
> newforms-admin: Fi
