Hi all,
I would like to know, when we can have HTTP3 support in apache webserver
stack. I know that apache not yet committed an affirmative date for
support, but even if it is tentative also, it's helpful to me.
Pls share the same if anyone has this info.
With Regards,
Venkatesh
I did:
# httpd -S
[Tue Sep 22 16:54:21.799963 2020] [so:warn] [pid 1419476:tid 139725243156800]
AH01574: module reqtimeout_module is already loaded, skipping
[Tue Sep 22 16:54:21.800135 2020] [so:warn] [pid 1419476:tid 139725243156800]
AH01574: module headers_module is already loaded, skipping
[
That file is for Debian-flavor distributions. On RedHat-flavors, a similar
file would be in /etc/httpd/conf.d if it exists (not in conf.modules.d
though). You can check which files have the actual config for a vhost by
running the command 'httpd -S'.
- Y
Sent from a device with a very small keybo
Where is "000-default.conf" file? I have not it!!
# ls /etc/httpd/conf.modules.d/
00-base.conf 00-proxy_timeout.conf 10-mod_security.conf
00-dav.conf 00-ssl.conf 10-proxy_h2.conf
00-lua.conf 00-systemd.conf 15-php.conf
00-mpm.conf 01-cg
Jason Long wrote:
When I visit my website by its IP address the welcome page of Apache showed, but
with"https://domain-name.net"; everything is OK. How can I block direct access
by IP or forward it to domain?
In the 000-default.conf put these lines:
RewriteEngine on
RewriteRule ^/ https://
Hello,
When I visit my website by its IP address the welcome page of Apache showed,
but with "https://domain-name.net"; everything is OK. How can I block direct
access by IP or forward it to domain?
I enabled "mod_rewrite" and my Virtual Host config is:
RewriteEngine on
RewriteCond %{SERVER_NAME
