Hongli Lai

_From [honglilai](https://code.google.com/u/[email protected]/) on February 04, 2013 11:45:07_ **Labels:** -Type-Defect Type-Enhancement

The structure that currently best represents per-app config, is ApplicationPool::Options. However this structure is incomplete: it only represents config that are relevant to ApplicationPool. So for example `PassengerMonitorLogFile` is not...

See also https://github.com/phusion/passenger-nodejs-websocket-demo/issues/2

The chunked encoding problem can be solved by setting Content-Length: 0 in the response, which will prevent Apache from setting Transfer-Encoding. ``` // Process WebSocket upgrade. Header upgrade = lookupHeader(headerData,...

Unfortunately not. If you need WebSockets, for the time being we recommend using Nginx, or using Passenger Standalone behind Apache + mod_proxy.

@vanboom That is correct, WebSockets do not work yet in the Apache version. For the time being, we recommend that you use the Nginx version, or Apache + Standalone in...

Thanks for reporting this. You hypothesize that the initializer is ignored. We should verify that. Can you add this to config/initializers/riiif.rb? raise 'error' Then start Passenger. Do you see the...

This isn't a problem in Passenger. You need to install the ruby-etc package: https://pkgs.alpinelinux.org/package/edge/main/x86/ruby-etc

I would call this neither a bug, nor expected behavior. I'm not really sure how to categorize this. It's definitely unwanted, but it's not caused by anything that's Passenger's fault....

Passenger Enterprise indeed already implements that, through the passenger_max_request_time option.