> I'm running a development website on an apache2
> instance tied to the port 8080. The website uses an error handler
> tied to the 404 error code in order to intercept some old urls
> and remap them to the new pages via the http protocol and
> the 'header redirect' command. This works on the server
Why not use mod_rewrite for this? Or even plain old mod_alias. For instance:
<Directory /www/dedasys.com/dedasys>
Redirect permanent /articles http://www.welton.it/articles
Redirect permanent /davidw http://www.welton.it/davidw
Redirect permanent /freesoftware http://www.welton.it/freesoftware
> running on the default port (80) but fails when the webserver
> runs on the port 8080 because the environment
> of the error handler retains 80 as port number.
> I checked this out by shutting down the regular apache
> server on the port 80 to avoid possible interferences
> and logging the other server's environment into the error
> log (load_env ENV; puts stderr $ENV(SERVER_PORT))
> As a consequence the command 'makeurl' (a quite simple
> wrapper of ap_construct_url) builds a wrong url and the
> requests are redirected to the wrong webserver. 'ap_construct_url'
> code is very simple too and left me clueless about the
> reason for this. I googled this problem but found out nothing.
> any idea? Is the core mishandling the error?
Seems weird... Can you create a test case for it?
> -- Massimo
>
> P.S. I also noticed that, after works on the server this list
> has been renamed as rivet-cvs. David, should we signal this to
> the infrastructure?
Looks like rivet-dev here.
--
David N. Welton
http://www.welton.it/davidw/
http://www.dedasys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
