User from the Internet can see the 3rd vhost site now. The current access
control directives are:
Order allow,deny
All from all
Now that Apache can route to the 3rd vhost block I edited the access
controls to tighten things down and enable localhost access as:
Order deny,allow
Deny from all
Allo
Starting to understand this better. Appending the public IP to the current
list of alias names in httpd.conf works as you said (for me).
ServerAlias [redacted alias] [redacted public IP]
Sent the link to a user- see what they say.
On Tue, Jun 25, 2013 at 1:31 PM, Eric Covener wrote:
> On Tue,
Hi,
Try using the password protect directories in mod_security until you find the
solution.
From: Eric Covener
To: users@httpd.apache.org
Sent: Tuesday, June 25, 2013 10:31 AM
Subject: Re: [users@httpd] Apache virtualhost order deny, allow works only on
On Tue, Jun 25, 2013 at 11:33 AM, Kirk Woellert wrote:
> That worked. I edited the /etc/host file on the linux client with a public
> IP, and I can get access to the 3rd vhost. Finally, get back to the original
> issue which started all this.
>
> I need to be able expose the site to certain decisi
That worked. I edited the /etc/host file on the linux client with a public
IP, and I can get access to the 3rd vhost. Finally, get back to the
original issue which started all this.
I need to be able expose the site to certain decision makers while its
under development. Hence why I tried Order, D
On Tue, Jun 25, 2013 at 11:12 AM, Kirk Woellert wrote:
> Ok, there are two clients in this thread, 1 is the client on the server
> console and is my personal linux system which is on the Internet. The
> /etc/hosts file on the server has an entry so that the alias in the vhost
> block resolves when
Ok, there are two clients in this thread, 1 is the client on the server
console and is my personal linux system which is on the Internet. The
/etc/hosts file on the server has an entry so that the alias in the vhost
block resolves when testing on the server. Are you saying I need to edit
the /etc/h
Hi Kirk,
Zitat von Kirk Woellert :
It's a good point but I need to able to access this site from one public IP
in particular. I thought an entry in /etc/hosts currently as:
127.0.0.1 [redacted alias for 3rd vhost]
would be sufficient but maybe not? If not, how can I get Apache to 'route'
to th
Trying everything- test php file i.e. info.php, also just did a 'touch' and
created an index.html, owned by the 3rd vhost user:group, chmod 775.
Can load the index.html on the local server console but not from the
Internet (using a physical path).
-Kirk Woellert
On Tue, Jun 25, 2013 at 10:35 AM,
On Tue, Jun 25, 2013 at 11:01 AM, Kirk Woellert wrote:
> It's a good point but I need to able to access this site from one public IP
> in particular. I thought an entry in /etc/hosts currently as:
>
> 127.0.0.1 [redacted alias for 3rd vhost]
>
> would be sufficient but maybe not? If not, how can I
It's a good point but I need to able to access this site from one public IP
in particular. I thought an entry in /etc/hosts currently as:
127.0.0.1 [redacted alias for 3rd vhost]
would be sufficient but maybe not? If not, how can I get Apache to 'route'
to that 3rd vhost? What would people typica
> As a reminder- I don't have a FQDN for the third vhost site- so I just made
> a /etc/host temporary entry as mentioned earlier in my post. Therefore when
> I try to check for public access, I'm always using a physical path in the
> browser as:
>
> http://[redacted public IP]/~[redacted user for 3
Are you only trying to open PHP files or do you get the same issue with CSS
and image files?
On Tue, Jun 25, 2013 at 10:30 AM, Kirk Woellert wrote:
> Hi, I looked at output of a "# httpd -S" command too- didn't see an
> obvious problem but here it is (pardon all the redaction):
> --
Hi, I looked at output of a "# httpd -S" command too- didn't see an obvious
problem but here it is (pardon all the redaction):
--
[root@[myhostname mysuperuser]# httpd -S
[Tue Jun 25 10:06:18 2013] [warn] NameVirtualHost *:443 has no VirtualHosts
VirtualHost configuration:
[Assigned
On Tue, Jun 25, 2013 at 8:39 AM, Kirk Woellert wrote:
> Update: Still have the same basic problem, I can access the vhost2 from the
> Internet, but can only access vhost3 from the localhost- not from the
> Internet. The behavior in my reply was not repeatable. I tried to completely
> open up acces
Update: Still have the same basic problem, I can access the vhost2 from the
Internet, but can only access vhost3 from the localhost- not from the
Internet. The behavior in my reply was not repeatable. I tried to
completely open up access to the vhost3 site by:
order allow,deny
allow all
But still
Its not file permissions -
So, I tried the suggestion. Now, in addition to access denied from the
public IP, access is also denied on the localhost (I tried the alias and a
physical path).
AND the site with a FQDN got redirected to the default Apache site
(/var/www). I was not expecting the current
>
> ServerName test
> ServerAlias test
> DocumentRoot /home/user3/public_html/test
>
> SuexecUserGroup test test
>
> Order Deny,Allow
> Deny from all
> Allow from xxx.xxx.xxx.xxx 127
>
Assuming its not the file permission have y
First time posting to the mail list-
Environment:
RHEL6
Apache v2.2
UserDir configured/works great
SuExec configured/works great
I have restricted access to user directories as follows:
Options MultiViews +ExecCGI
AddHandler cgi-script .cgi .pl
Order Deny,Allow
Deny from All
An
19 matches
Mail list logo
