Re: [users@httpd] Configuring redirects from http to https

I quickly discovered that when a test of host2 returned the host1 index page. So I changed the second VirtualHost address to be the same as host1 (aaa.bbb.ccc.ddd:80). That seems to have solved the problem. So now the actually working *.conf is as follows (as a template?): Listen 80 # Listen

Re: [users@httpd] Configuring redirects from http to https

On Fri, Nov 30, 2018 at 1:40 PM Jack M. Nilles wrote: > # http redirect >>> >>> >>> >>> >> Note you have an error there, the incoming request will be matched to only one list of matching VirtualHosts, host1.com alone on the first, and host2 alone on the second list. You surely meant these to

Re: [users@httpd] Configuring redirects from http to https

I just added a Listen 80 line at the top of my config file, changed both

Re: [users@httpd] Configuring redirects from http to https

Is there a Listen 80 directive anywhere in your configuration files? On Sat, Dec 1, 2018, 15:22 Jack M. Nilles I have checked the port 80 logs: they are empty. I concluded that the > problem might lie not with Apache but with the server port configuration. > > So I checked the ports on the

Re: [users@httpd] Configuring redirects from http to https

I have checked the port 80 logs: they are empty. I concluded that the problem might lie not with Apache but with the server port configuration. So I checked the ports on the server (netstat -nat | grep LISTEN): 80 is not listed among the listening. I checked the firewall configuration on the

Re: [users@httpd] Configuring redirects from http to https

Good point. I will add logging to port 80 and see what happens. - To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org For additional commands, e-mail: users-h...@httpd.apache.org

Re: [users@httpd] Configuring redirects from http to https

Do you have logging on the port 80 "redirect" virtualhost, and is that what you are looking at? If you are seeing entries from use of the https instance it sounds like you are reviewing the port 443 virtualhost logging, not the logs for port 80. > Date: Friday, November 30, 2018 16:37:02 -0800 >

Re: [users@httpd] Configuring redirects from http to https

I got nothing out of that filter. I note that response to my queries produced: [30/Nov/2018:14:57:10 -0800] "-" 408 - "-" "-" on a few occasions. > On 30 Nov 2018, at 15:48, Filipe Cifali wrote: > > grep -i “mismatch” on it may provide something, your config seems correct, > which is weird

Re: [users@httpd] Configuring redirects from http to https

grep -i “mismatch” on it may provide something, your config seems correct, which is weird On Fri, 30 Nov 2018 at 21:17 Jack M. Nilles wrote: > I have an access log and an error log. The error log doesn't show much for > today. The access log is full of entries from those who have used the https

Re: [users@httpd] Configuring redirects from http to https

I have an access log and an error log. The error log doesn't show much for today. The access log is full of entries from those who have used the https address. What should I be looking for to detect the http failures? - To

Re: [users@httpd] Configuring redirects from http to https

Turn log level and attach log outputs in pastebin/gist or even here (just the text) of a full access, from begin to end of the request. Also, use cURL locally at the httpd server to try to reproduce it On Fri, 30 Nov 2018 at 20:14 Jack M. Nilles wrote: > The interchange also had no effect. Nor

Re: [users@httpd] Configuring redirects from http to https

The interchange also had no effect. Nor did changing the line to: RedirectPermanent / https://www.host1.com > On 30 Nov 2018, at 13:52, Jack M. Nilles wrote: > > This doesn't work for me either with or without the trailing slash. I'll try > it with the name and alias

Re: [users@httpd] Configuring redirects from http to https

This doesn't work for me either with or without the trailing slash. I'll try it with the name and alias lines interchanged. > On 30 Nov 2018, at 12:27, Jeff Cox wrote: > > Try it like this. This is mine except my server name and server alias are > reversed. > > > ServerName www.abc.com

Re: [users@httpd] Configuring redirects from http to https

Try it like this. This is mine except my server name and server alias are reversed. ServerName www.abc.com ServerAlias abc.com Redirect 301 / https://www.abc.com/ -- Jeff Cox j...@jeffpcox.com On Fri, Nov 30, 2018 at 1:40 PM Jack M. Nilles wrote: > I tried adding trailing

Re: [users@httpd] Configuring redirects from http to https

I tried adding trailing slashes as follows, but the result was the same: a 111 error. Did I misinterpret your comment? > # http redirect > > ServerName www.host1.com > ServerAlias host1.com *.host1.com >Redirect "/" "https://www.host1.com/; # Here > > > > ServerName www.host2.com >

Re: [users@httpd] Configuring redirects from http to https

The error I mentioned turns out to be a Squid error. I'm beginning to think I'm getting a false alarm from the browser since, if I connect through a different network, I have no problem with the redirects. I'll have to test some more from different locations. So forget it for now, thanks. >

Re: [users@httpd] Configuring redirects from http to https

The (111) is a networking issue because you're not matching the trailing slashes with your redirects. On Thu, Nov 29, 2018 at 6:06 PM Jonathon Koyle wrote: > Can you reproduce the issue and provide some logs, and maybe more > information about the actual response? the 1xx range isn't supposed

Re: [users@httpd] Configuring redirects from http to https

Can you reproduce the issue and provide some logs, and maybe more information about the actual response? the 1xx range isn't supposed to be an error code in HTTP. On Thu, Nov 29, 2018 at 3:25 PM Jack M. Nilles wrote: > I have the following configuration file covering two virtual hosts: > > #

[users@httpd] Configuring redirects from http to https

I have the following configuration file covering two virtual hosts: # http redirect ServerName www.host1.com ServerAlias host1.com *.host1.com Redirect "/" "https://www.host1.com; ServerName www.host2.com ServerAlias host2.com *.host2.com Redirect / https://www.host2.com # https