Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Passenger on Apache doesn't support the Rack Hijack API? #1497

Closed
ylluminate opened this issue May 5, 2015 · 3 comments
Closed

Passenger on Apache doesn't support the Rack Hijack API? #1497

ylluminate opened this issue May 5, 2015 · 3 comments

Comments

@ylluminate
Copy link

We're having an issue wherein Nginx is working, but Apache is not for the Rack Hijack API. voltrb/volt#192 (comment)

Can you confirm this @FooBarWidget or can we provide some additional information that will help to resolve this problem?

@FooBarWidget
Copy link
Member

Hijacking in Apache should work, except if you're hijacking the socket for the purpose of WebSockets (because of #1202). Can you provide a reproducible example that highlights your problem?

@ylluminate
Copy link
Author

Okay, so yes, it is indeed an issue with websockets and apache in this case. I haven't had a chance to dig through too much. How soon are we looking at in terms of seeing a resolution to #1202? I see a reference there for 5.0.5 and 5.1.0 on this issue...

@FooBarWidget
Copy link
Member

Not very soon. My best guess would be that we can start working on that half a year from now.

There are workarounds though. You can run your app in Passenger Standalone (preferably with the builtin engine for optimal performance, though the Nginx engine works too) and setup a reverse proxy to Apache using mod_proxy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants