On Tue, Jun 14, 2022 at 07:21 Tom Browder wrote:
> On Tue, Jun 14, 2022 at 07:15 Eric Covener wrote:
>
Use developer tools in the browser or a command-line client to look at
>> the response headers. Share them here.
>
>
Will a curl response be useful? Or do I need wireshark?
-Tom
On Tue, Jun 14, 2022 at 07:15 Eric Covener wrote:
> > I have noticed the long page delays for seeing refreshed paged for my
> sites for some time in all browsers and on all OSs. Any suggestions?
>
> Use developer tools in the browser or a command-line client to look at
> the response headers. Sh
On Tue, Jun 14, 2022 at 8:13 AM Tom Browder wrote:
>
> I am using a long ssl session cache settings in my httpd.conf file. Will that
> delay viewing a refreshed page during a session?
No.
> I have noticed the long page delays for seeing refreshed paged for my sites
> for some time in all brows
I am using a long ssl session cache settings in my httpd.conf file. Will
that delay viewing a refreshed page during a session?
I have noticed the long page delays for seeing refreshed paged for my sites
for some time in all browsers and on all OSs. Any suggestions?
Thanks.
-Tom
[Mon Sep 15 11:42:04.211290 2014] [core:error] [pid 18302:tid 140171735451392] (36)File
name too long: [client xxx.xx.x.xxx:53717] AH00036: access to //_aliases failed (filesystem path '/), referer:
http://xx.xx.xx.xxx/index.html
Thanks,
That error message doesn't appear to be from t
ver that works fine with long URLs.
>>
>> [Mon Sep 15 11:42:04.211290 2014] [core:error] [pid 18302:tid
>> 140171735451392] (36)File name too long: [client xxx.xx.x.xxx:53717]
>> AH00036: access to //_aliases failed (filesystem path
>> '/), referer: http://xx
fine with long URLs.
>>
>> [Mon Sep 15 11:42:04.211290 2014] [core:error] [pid 18302:tid
>> 140171735451392] (36)File name too long: [client xxx.xx.x.xxx:53717]
>> AH00036: access to //_aliases failed (filesystem path
>> '/), referer: http://xx.xx.xx.xxx/index.
name too long: [client xxx.xx.x.xxx:53717]
AH00036: access to //_aliases failed (filesystem path
'/), referer: http://xx.xx.xx.xxx/index.html
Thanks,
That error message doesn't appear to be from the httpd server itself
(ie, that message doesn't appear anywhere in the source code
happening when the URL is not related to a file on the file system?
The URL is rewritten, then proxied to another server that works fine
with long URLs.
[Mon Sep 15 11:42:04.211290 2014] [core:error] [pid 18302:tid
140171735451392] (36)File name too long: [client xxx.xx.x.xxx:53717]
AH00036: access
Hi All,
I have compiled apache 2.4.3.
I am getting below error while starting it.
Error1 :-
AH00526: Syntax error on line 139 of httpd.conf:
ProxyPass Can't find 'byrequests' lb method
Error2 :-
ProxyPass worker name file_name too long
Kindly help me how to fix this iss
example,dc=com
AuthLDAPBindPassword secret
AuthLDAPURL ldap://
192.168.56.110:389/dc=example,dc=com?sAMAccountName?sub?(objectClass=*)
Require valid-user
...
--=--
It works, but it takes far too long.
I analyzed the traffic with tcpdump.. the timestamps show ex
Bruce Hyatt wrote:
On Sat, Dec 20, 2008 at 6:09 AM, Dzilberte Bekode wrote:
Hi
thanks a lot man.
Now I know how it works.
That's the important thing.
But what I don't understant is why is it so slow only when I want submit
form, because page is running fast.
Anyway its working now after I've
On Sat, Dec 20, 2008 at 6:09 AM, Dzilberte Bekode wrote:
> Hi
> thanks a lot man.
> Now I know how it works.
> But what I don't understant is why is it so slow only when I want submit
> form, because page is running fast.
> Anyway its working now after I've deleted everything in hosts file.
> I re
Dzilberte Bekode wrote:
Hi
thanks a lot man.
Now I know how it works.
But what I don't understant is why is it so slow only when I want submit
form, because page is running fast.
Anyway its working now after I've deleted everything in hosts file.
I realy don't understant. It can be empty?
Than
pozdravom Janci Siser
--- On Fri, 12/19/08, André Warnier wrote:
From: André Warnier
Subject: Re: too long
To: users@httpd.apache.org
Date: Friday, December 19, 2008, 11:34 AM
Dan Poirier wrote:
[...]
.. and he is right.
It really looks like a DNS problem, *on Dzilberte's workstation side*
Dan Poirier wrote:
[...]
.. and he is right.
It really looks like a DNS problem, *on Dzilberte's workstation side*.
I connected to the site and submitted the contact form. The response is
immediate (less than 1 second).
For Dzilberte :
I also do not know how much you know about how HTTP works
Delays that are multiples of a minute always make me look for DNS
problems, since often a failed DNS lookup will timeout in one minute.
It could be the client is failing to look up the host. If the client
has multiple DNS servers defined, it could be that the first couple are
not responding and i
----
S pozdravom Janci Siser
--- On Fri, 12/19/08, André Warnier wrote:
From: André Warnier
Subject: Re: too long
To: users@httpd.apache.org
Date: Friday, December 19, 2008, 6:01 AM
Dzilberte Bekode wrote:
I'm running Apache/2.2.3 (Debian) PHP/5.2.0-8+etch13 mod_ssl/2.2.3
OpenSS
Dzilberte Bekode wrote:
I'm running Apache/2.2.3 (Debian) PHP/5.2.0-8+etch13 mod_ssl/2.2.3
OpenSSL/0.9.8c Server at 81.89.49.231 Port 80.
[...]
> Any Ideas what may be wrong?
No, because there may be many reasons, and you do not really give enough
information to orient us.
But maybe you
HI
I'm running Apache/2.2.3 (Debian) PHP/5.2.0-8+etch13 mod_ssl/2.2.3
OpenSSL/0.9.8c Server at 81.89.49.231 Port 80.
The problem is that when I submit any form (contact form or register
form) on my webpages, it takes too long to proceed (around 2 minutes)
It's prett
On 7/25/06, Peter Posselt Vestergaard <[EMAIL PROTECTED]> wrote:
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Joshua Slive
> Sent: 24. juli 2006 17:30
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] refer
Peter
> -Original Message-
> From: Peter Posselt Vestergaard [mailto:[EMAIL PROTECTED]
> Sent: 25. juli 2006 07:35
> To: users@httpd.apache.org
> Subject: RE: [EMAIL PROTECTED] referer header field too long?
>
> > -Original Message-
> > From: [EMAIL PROTECTED] [ma
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of
> Joshua Slive
> Sent: 24. juli 2006 17:30
> To: users@httpd.apache.org
> Subject: Re: [EMAIL PROTECTED] referer header field too long?
>
> On 7/24/06, Peter Posselt Veste
On 7/24/06, Peter Posselt Vestergaard <[EMAIL PROTECTED]> wrote:
Hi
We have a number of Apache HTTP servers installed all with version
2.0.54.
Lately we have seen a number of "400 Bad Request" in the error logs, and
after a lot of testing we have found that this happens then the
"Referer" HTTP he
Hi
We have a number of Apache HTTP servers installed all with version
2.0.54.
Lately we have seen a number of "400 Bad Request" in the error logs, and
after a lot of testing we have found that this happens then the
"Referer" HTTP header field in the request contains a URL that it more
than 200 char
25 matches
Mail list logo
