On Thu, Oct 31, 2024 at 2:12 PM Marc <m...@f1-outsourcing.eu> wrote: >
[...] > > If you're using ip tables, you can re-route the request to a different > > TCP port and configure a vhost that serves the chosen document for any > > request to any path. [...] > Yes this is probably the most efficient. I am surprised this seems to work > for http and https traffic. Do you mean to the same port for http and https? Or are you surprised that it works for https at all? The latter shouldn't be a surprise - the clients will not be able to know about the port remapping, and as long as you supply a valid certificate, they will be happy. > I am testing with this now. Only thing I probably am stuck with is having > this in GlobalLog. you can turn off your GlobalLog if you add an [env=[!]environment-variable] statement and setenv that environment-variable in your new vhost. https://httpd.apache.org/docs/2.4/mod/mod_log_config.html#globallog > I prefer to return there everything with 4xx return code, but can't get this > for / Use an empty directory as the documentroot, disable mod_autoindex. Use a highish debug level to check what your rewriteRules are actually doing. Also, if you had written what you're actually getting for /, what you've tried so far to get the desired result, and what exactly your current httpd configuration does, that would have helped the readers of this list to help you. Rainer --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org
