-
Notifications
You must be signed in to change notification settings - Fork 1
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
Why we can't read stream during the access phase #2
Comments
@ryeyao If we can't read the TCP stream during the access phase,which phase can we do that? |
@daxiong380380 It would be nice if you descibe the problem more specificlly for it might help others reading this issue.
Try to read socket within content_by_lua* directive. Note that this directive can not coexist with proxy_pass. |
@ryeyao I'm sorry to that ,I mean I can't read the stream during the access phase after patched nginx-allow_override_stream_access_handler.patch & nginx-init_session_before_access_handler.patch . As you say, we can read socket within content_by_lua directive,but if I use the content* directive,I can't use proxy_pass.In my project,I plan to read and parse the socket,then I can choose the proxy address,so I can send the socket stream to the address that I have set. |
@ryeyao |
Correct (hopefully). (sorry for taking so long to reply..)
There should be several ways to achieve this (which I am not familiar with). You may ask openresty group for some help. |
After I put a patch to nginx,I find that nginx can't read stream,can we do any thing to solve the problem
The text was updated successfully, but these errors were encountered: