Check the dns resolution for the xyz host.
Sent from my phone
On Dec 9, 2010 1:24 PM, "Craig A. James" wrote:
We operate one public web site and about 20 private web sites. They're all
the same server, running the same Apache server instance
(2.2.14-5ubuntu8.3).
Most customers get excellent p
We operate one public web site and about 20 private web sites. They're all the
same server, running the same Apache server instance (2.2.14-5ubuntu8.3).
Most customers get excellent performance, but two customers get terrible
response times, but only on *some* of the VirtualHosts. They get ex
- "Raphael Bauduin" wrote:
> Hi,
>
> I have an internal application where users authenticate against an
> LDAP.
> I wanted to do this:
> SuExecUserGroup %{AUTHENTICATE_uid} www-data
>
> but it isn't accepted. Is there a way to do this, or does that mean
> modifying the suexec executable?
- "Ben Short" wrote:
> Hi,
>
> Is it safe to have 2 vhosts logging to the same log file?
If by that you mean only having an ErrorLog in server context
then yes. Perfectly safe. Otherwise you're calling for trouble.
n.b.: Trunk has a very customizable ErrorLogFormat:
http://httpd.apache.or
- "Anthony Dodson" wrote:
> Hello.
>
>
> I am running apache 2.2.15. I would like to use mod_cache, and I need
> a good way for SysAdmins to manually clear the cache for specific URLs
> when needed, but not allow users to do so from their browser.
>
>
> It seems that when a browser sends
Hello.
I am running apache 2.2.15. I would like to use mod_cache, and I need a good
way for SysAdmins to manually clear the cache for specific URLs when needed,
but not allow users to do so from their browser.
It seems that when a browser sends headers Cache-Control: no-cache or
Pragma: no-cache,
I am seeing this error come up every once in a while in a log I am
reviewing. I have tried to find its meaning on google and find lots of
way you can try fixing it but not what it means.
This is the error:
[error] mod_jk child init 1 -2
At this point, I don't need to know how to fix this erro
Hello,
On 08.12.2010 16:01, Eric Covener wrote:
.. I propose a less quirky configuration, for example
with "ServerName .. exclusive"
So it would handshake with the "wrong" information and serve the wrong
virtualhosts error documents?
The "exclusive" defined vhost would do what the second vho
On Wed, Dec 8, 2010 at 9:54 AM, wrote:
> Hello,
>
> On 08.12.2010 15:03, Eric Covener wrote:
>>
>> And at least 50% of the world would think whatever you intuitively
>> expect to happen in this case is quirky. That's why there's a
>> configuration file.
>
> I expect nothing to happen intuitively.
Hello,
On 08.12.2010 15:03, Eric Covener wrote:
And at least 50% of the world would think whatever you intuitively
expect to happen in this case is quirky. That's why there's a
configuration file.
I expect nothing to happen intuitively.
What happens now, serving any-SSL violating the vhost def
Hi,
I have an internal application where users authenticate against an LDAP.
I wanted to do this:
SuExecUserGroup %{AUTHENTICATE_uid} www-data
but it isn't accepted. Is there a way to do this, or does that mean
modifying the suexec executable?
Thanks for your help
Raphaël
--
Web database: h
On Wed, Dec 8, 2010 at 7:43 AM, wrote:
> Hello,
>
> On 08.12.2010 13:31, Eric Covener wrote:
>>>
>>> "ServerName ... exclusive" directive for
>>> the config (and logic behind) could make sense, ...
>>
>> This facility is effectively already there by creating a default
>> (first-listed) name-based
Hello,
On 08.12.2010 14:13, Tom Evans wrote:
...
And the experienced user has seen these warnings often, so he regularly
clicked on "I understand the risks" and accepted the ssl session anyway -
and it's even wiser in most cases to do because mostly you're better off (in
web 2.0 services for exa
On Wed, Dec 8, 2010 at 12:55 PM, wrote:
> Hello,
>
> On 08.12.2010 13:45, Tom Evans wrote:
>>>
>>> .. but at this point apache knows that there is something wrong with the
>>> request or the configuration, and should throw an error instead of
>>> serving
>>> the wrong data.
>>
>> Typically, you d
Hello,
On 08.12.2010 13:45, Tom Evans wrote:
.. but at this point apache knows that there is something wrong with the
request or the configuration, and should throw an error instead of serving
the wrong data.
Typically, you don't even get to that point. Most browsers will throw
a fit if they r
On Wed, Dec 8, 2010 at 12:21 PM, wrote:
> Hello,
>
> On 08.12.2010 12:48, Tom Evans wrote:
>>
>> Until the incoming request has been received and decrypted, apache has
>> no clue that the domain requested was 'not-ssl-configured-domain.xx'.
>> That's kind of the point of SSL.
>
> Ok, thanks for p
Hello,
On 08.12.2010 13:31, Eric Covener wrote:
"ServerName ... exclusive" directive for
the config (and logic behind) could make sense, ...
This facility is effectively already there by creating a default
(first-listed) name-based virtual host and handling unspecified
domains that show up on
> "ServerName ... exclusive" directive for
> the config (and logic behind) could make sense, or maybe it exists and my
> weary eyes overread it.
This facility is effectively already there by creating a default
(first-listed) name-based virtual host and handling unspecified
domains that show up on
Hello,
On 08.12.2010 12:48, Tom Evans wrote:
Until the incoming request has been received and decrypted, apache has
no clue that the domain requested was 'not-ssl-configured-domain.xx'.
That's kind of the point of SSL.
Ok, thanks for pointing that out.
Apache determines which vhost to use to
On Wed, Dec 8, 2010 at 11:13 AM, wrote:
>
> Just to make it clear:
> What I perceived as a .. quirky behaviour of apache was that it did _not_
> throw an error when https://not-ssl-configured-domain.xx is requested.
> How to run several https domains with one IP was not my challenge.
>
> / Bernd
Hi,
Is it safe to have 2 vhosts logging to the same log file?
Regards
Ben Short
-
The official User-To-User support forum of the Apache HTTP Server Project.
See http://httpd.apache.org/userslist.html> for more info.
To unsubscr
Hello,
On 08.12.2010 11:38, Matus UHLAR - fantomas wrote:
Now what happens to my surprise is that /phppgadmin is accessible via
all my virtual hosts, not just the one (base host) where it is
defined.
...
On 07.12.10 20:27, Joost de Heer wrote:
SSL namebased virtualhosting will not work.
..
He
> > Now what happens to my surprise is that /phppgadmin is accessible via
> > all my virtual hosts, not just the one (base host) where it is
> > defined.
>
> All your virtual hosts or all your SSL virtual hosts?
>
> > https://onesite.com/phppgadmin
> > https://twosite.com/phppgadmin
On 07.12.10
On 07.12.10 19:08, b...@kanka.de wrote:
> I've switched to a new debian server with apache 2.2.9 and installed the
> 'phpgadmin'
> tool via a debian package.
> This copies the php sources outside of /var/www and sets an 'alias ..'
> directive in /etc/apache2/conf.d/
> Now what happens to my surp
Hi,
Thanks for that helpful post, changing proxy setting to proxy-sendchunks
did actually the trick! However I wonder which timeout could have been
hit, at least KeepAliveTimeout and ProxyTimeout were set to a higher
value than these 40 secs. Maybe a timeout on backend site...
Br,
Elmar
-Ori
25 matches
Mail list logo
