To clarify a bit regarding what exactly the regression is:
This works in earlier Apache 2.4 versions:
AddHandler proxy:unix:/run/sockets/uwsgi-fcgi.sock|uwsgi:// .php
But with 2.4.60 and newer, this results in an error message:
AH10097: error parsing URL //: Invalid host/port
If one then tries
Hi,
I see that there is a regression with uwsgi when using Apache 2.4 fixes
introduced in July with Apache 2.4.60/2.4.61, this also goes for the recent
regression fixes for Apache 2.4.62 released by Debian yesterday (DSA
5729-2).
The uwsgi regression is described here, but apparently has not reac
On Fri, Nov 11, 2011 at 10:57, Jan Ingvoldstad wrote:
>
> Has anyone seen similar problems?
>
I can't hear the crickets, but apparently, the answer is "no".
Does anyone then have any useful suggestions on how to go about debugging
this?
The documentation for the cac
Hi.
I have a frustrating problem, which I'm not quite able to debug properly.
I have a webserver running Apache 2.2.21 compiled as worker-MPM with a
suhosin 0.9.32.1-enabled PHP 5.2.17 (using "phpize", not patching)
under suphp 0.7.1, with mod_security 2.6.1 and modsecurity_crs 2.2.1
plus modsecu
On Wed, Oct 7, 2009 at 10:55 AM, André Warnier wrote:
> 1) *don't use Notepad to edit HTML pages*. Use a real editor, properly
> aware of character sets and encodings, and which will highlight incorrect
> UTF-8 characters.
> Notepad has a big problem when saving UTF-8 encoded files : it writes a