[users@httpd] Weird access logs

Hi there, We're seeing some weird behaviour in our access logs. For around 13 minutes we see entries from requests received several minutes before it actually gets logged (the two timestamps on the same line are up to 13 minutes apart! ). The number to the far right is %D - the response time (mic

[users@httpd] VirtualHost conditionless HSTS

Hello! Working with Apache 2.4. I wanted to configure an https host with HSTS: [...] Header set Strict-Transport-Security "max-age=31556952" Require all granted [...] [...] This works fine. However as soon as I require HTTP authentication on apache level,

Re: [users@httpd] VirtualHost conditionless HSTS

> Neither provides the HSTS header to an unauthenticated user. Is there > a simple way to inject the HSTS (or any) header to unauthenticated > users? If it's the 401 that you want to have the header, you'll need Header always set ...

Re: [users@httpd] VirtualHost conditionless HSTS

Oh thanks, this is exactly I was looking for. I totally missed it in the documentation. It's there. Thank you. 2014-11-13 14:30 GMT+01:00 Eric Covener : >> Neither provides the HSTS header to an unauthenticated user. Is there >> a simple way to inject the HSTS (or any) header to unauthenticated >

[users@httpd] index.php ist used (internally) when /index.php/ is requested

Hello list, Strange thing. If a request is made for a directory URL where the directory contains a .php then this request is translated to just the php file and php is executed. (/index.php/ --> /index.php) In my opinion this should not happen. Since a directory is requested and index.php is

Re: [users@httpd] index.php ist used (internally) when /index.php/ is requested

This is usually the intended behavior. Many PHP frameworks use PATH_INFO to handle requests. See the documentation for AcceptPathInfo: http://httpd.apache.org/docs/current/mod/core.html#acceptpathinfo - Y On Thu, Nov 13, 2014 at 10:25 AM, Christoph Gröver wrote: > > Hello list, > > Strange thi

Re: [users@httpd] index.php ist used (internally) when /index.php/ is requested

Hello list, > This is usually the intended behavior. Many PHP frameworks use > PATH_INFO to handle requests. > > See the documentation for AcceptPathInfo: > http://httpd.apache.org/docs/current/mod/core.html#acceptpathinfo Thanks Yehuda. I see why this is being used. Is this the default for a l

[users@httpd] Problem with mod_proxy and chunked content

Hi, We have a problem with mod_proxy and chunked content. We use mod_proxy to selectively request pages from a second site, the ProxyPass and ProxyPassReverse statements are in the vhost file. Nearly all requests are OK, Except for one type of request which can't be handled properly. We use SAML

Re: [users@httpd] Problem with mod_proxy and chunked content

The transfer encoding header is missing, right? Sendt fra min iPhone > Den 13. nov. 2014 kl. 18.13 skrev Blomme Dieter : > > Hi, > > We have a problem with mod_proxy and chunked content. > We use mod_proxy to selectively request pages from a second site, the > ProxyPass and ProxyPassReverse st

Re: [users@httpd] Problem with mod_proxy and chunked content

Yes, but I thought that if that header is missing, it should still check if the data is chunked, is that incorrect? > On 13 Nov 2014, at 18:52, Stefan Magnus Landrø > wrote: > > The transfer encoding header is missing, right? > > Sendt fra min iPhone > >> Den 13. nov. 2014 kl. 18.13 skrev Bl