Good evening,On 3/9/07 at 7:54 PM +0100, Matt S Trout <[EMAIL PROTECTED]> wrote:
The above error makes sense in the context of frontend/backend apache with rewrite rules. RewriteRule ^/login(.*)$ http://%{HTTP_HOST}:8627/progs/login$1 [P] RewriteRule ^/progs/(.*)$ http://%{HTTP_HOST}:8627/progs/$1 [P]That's kinda broken, it's relying on the request header which a browser could easily cock up.
Fair enough, although I've seen heaps of examples using %{HTTP_HOST} so I followed along.
I suspect %{REMOTE_HOST} would be better (see the mod_rewrite docs for
more info)
REMOTE_HOST seems to be the client host name, not the server. So I don't think that's the one you meant. Did you mean SERVER_NAME instead? Since SERVER_NAME seems to give the value I expect, I'll switch to using that. Still doesn't really solve the core issue though.
When I generate a URI string with $c->uri_for(...) and HTTPS=on, then I get :443 as part of the URI string. What can I do in my Catalyst config (or elsewhere) to prevent :443 being included in the URI string?
Thanks, Charlie -- Charlie Garrison <[EMAIL PROTECTED]> PO Box 141, Windsor, NSW 2756, Australia O< ascii ribbon campaign - stop html mail - www.asciiribbon.org http://www.ietf.org/rfc/rfc1855.txt _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
