Hi Graham, I have applied that fix to mod_wsgi 2.3 and it fixed the  
problem. Thanks.

I see you've applied the fix to 3.0 and 2.4 so will upgrade to one of  
those when they are released.

Cheers,
Chris Miles

On 02/03/2009, at 12:59 PM, Graham Dumpleton wrote:

>
> See:
>
>  http://code.google.com/p/modwsgi/issues/detail?id=132
>
> Don't understand why this has only started cropping up recently when
> technically should have always been a problem.
>
> Apply the fix and see if problem goes away.
>
> Graham
>
> 2009/3/2 Chris Miles <[email protected]>:
>>
>> I've got an odd problem, serving a Pylons (0.9.7) app with mod_wsgi
>> (2.3; apache 2.0.63) on Solaris 10.  The app runs fine, however  
>> static
>> files are truncated to 0 bytes (with a 200 response).
>>
>> e.g. this is what wget sees:
>>
>>    $ wget http://pylonsapp.dev.server.local/css/style.css
>>    --01:28:17--  http://pylonsapp.dev.server.local/css/style.css
>>               => `style.css'
>>    Resolving pylonsapp.dev.server.local... 172.16.102.109
>>    Connecting to pylonsapp.dev.server.local|172.16.102.109|:80...
>> connected.
>>    HTTP request sent, awaiting response... 200 OK
>>    Length: 6,789 (6.6K) [text/css]
>>
>>     0% [                 ] 0             --.--K/s
>>
>>    01:28:19 (0.00 B/s) - Connection closed at byte 0. Retrying.
>>
>> The browser happily accepts the 0 byte response and displays an empty
>> page.
>>
>> I was working around this by serving the static files directly from
>> Apache, but it still bothered me.
>>
>> Today I changed the Apache config to use a wsgi daemon process  
>> instead
>> (also disabling the Alias directives so static files are served by  
>> the
>> app again) and the static files are served properly now.
>>
>> I post this here in case anyone else stumbles over the same problem.
>>
>> My original config (non daemon process) was simply:
>>
>>    <VirtualHost 0.0.0.0:80>
>>        ServerName          pylonsapp.dev.server.local
>>        ServerAlias         pylonsapp.dev
>>        ErrorLog            /var/log/pylonsapp/error.log
>>        CustomLog           /var/log/pylonsapp/access.log combined
>>        LogLevel debug
>>        WSGIScriptAlias     / /export/project/pylonsapp/dispatch.wsgi
>>        WSGIPassAuthorization On
>>        <Directory /export/project/pylonsapp>
>>            Order deny,allow
>>            Allow from all
>>            Options FollowSymLinks
>>        </Directory>
>>    </VirtualHost>
>>
>> And the new config using daemon process is:
>>
>>    <VirtualHost 0.0.0.0:80>
>>        ServerName          pylonsapp.dev.server.local
>>        ServerAlias         pylonsapp.dev
>>        ErrorLog            /var/log/pylonsapp/error.log
>>        CustomLog           /var/log/pylonsapp/access.log combined
>>        LogLevel debug
>>        WSGIScriptAlias     / /export/project/pylonsapp/dispatch.wsgi
>>        WSGIPassAuthorization On
>>        WSGIDaemonProcess pylonsapp.dev.server.local display-name=%
>> {GROUP}
>>        WSGIProcessGroup pylonsapp.dev.server.local
>>        <Directory /export/project/pylonsapp>
>>            Order deny,allow
>>            Allow from all
>>            Options FollowSymLinks
>>        </Directory>
>>    </VirtualHost>
>>
>> Cheers,
>> Chris Miles
>>


--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"modwsgi" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/modwsgi?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to