David E. Wheeler wrote:
Fellow mod_perlers,
<snip>
Note that the hosthame is "benedict.local". Now I often just use localhost when
using Bricolage, and most of the time that works fine. But there is one
JavaScript-triggered redirect button that looks like this:
window.location.href = '/admin/profile/dest?id=1024'
And when I click it, The request goes to mod_perl and I see it come through the
access handler and the fixup handler as a request to localhost. But then the
PerlReponseHandler never fires! Instead, I see another request come in for the
same URL path, but this time for the host name benedict.local. It's almost as
if something in Apache or mod_perl is seeing that the request is for a
different domain name and helpfully trying to redirect. But it's not helpful (I
get a new login screen), and I don't understand why the same thing doesn't
happen for other requests.
Is there something like that in mod_perl2 and I'm just missing it? Or is it
more likely that there's some other mysterious bit of code in Bricolage that's
doing it and I just haven't found it yet? If the latter, what comes between the
PerlFixupHandler and PerlResponseHandler? Because in that first request, the
fixup handler fires but the response handler never does.
This smells like a UseCanonicalName On + mod_dir redirect to me. If the
directory /admin/profile/dest exists in the document root, there's a
good chance it is.
HTH,
Adam