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. > On

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 t

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: > > # ht

Re: [users@httpd] The Require Directives

You might try this, with some simple testing it seems to work... Require host usurf.usu.edu denied Require host c01622.usurf.usu.edu Require not host usurf.usu.edu Require ip 0.0.0.0/1 Require not host usurf.usu.edu Require ip 1

[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

[users@httpd] This is done by ensuring that the web server can write to these locations.

I want to set up a folder so that I can use a plugin in wordpress, the instructions work up to the point where I get this direction, but I don't know how to ensure that the apache instance has write access to the folder. I have admin rights. Suggestions? Reference? TIA Dave -- In modern fantas

Re: [users@httpd] The Require Directives

Sorry this is turning out to be so confusing! What I'm hoping to do, in pseudo-config would be something like this: Require not host bigdomain.com . ## nobody from the entire domain gets in! Require host buddy.bigdomain.com ## except this single client Require all granted

Re: [users@httpd] The Require Directives

So, you want to restrict access to the host to a single machine on a specific domain with a non-static IP, OR to any machine not on the domain? On Thu, Nov 29, 2018 at 12:34 PM Bill Tantzen wrote: > No that's not exactly what I meant. What I mean is something like > this -- although actually ty

Re: [users@httpd] The Require Directives

No that's not exactly what I meant. What I mean is something like this -- although actually typing it seems like it can't possibly be done: Require not host xxx.com Require host ok.xxx.com I realize "not host" is not allowed here, but it maybe helps explain what I want to do: Block an enti

Re: [users@httpd] The Require Directives

You want to only allow access to a server at a specific hostname, (that is how I understand you question). One way, that would work, is something like Listen 80 # This is the default host for this port (assuming it is the first declaration for a host on this port) all server names that do n

[users@httpd] The Require Directives

Experts, My environment is RHEL7 and apache 2.4.6 I am looking for the seemingly tricky combination of directives (Require, RequireAll, RequireAny...) that will allow me to deny access to an entire domain except for, say, one particular host. For instance, how do deny access to yyy.zzz.com e