But only in production does reject_unauthorized_connection get returned because request.params is empty.
Not sure if this is user error or a bug but it's very strange that this happens only on production. Is there anything that a production configuration could cause anycable to not parse request.params? Thanks!
Tell us about your environment
Ruby version: 2.6.6
Rails version: 6.0.3
anycable
gem version: 0.6.5anycable-rails
gem version: 0.6.5grpc
gem version: 1.28.0What did you do?
Connected to an anycable socket URL with query parameters.
What did you expect to happen?
Expected to be able to read the query parameters in connection.rb via request.params
What actually happened?
request.params is empty
Hey, I have this issue only in production mode. When developing locally the issue doesn't occur.
When trying to connect to
wss://api.test.to:8443/live?uid=yyy&token=xxx
I am usually able to read
request.params[:token]
with my authentication code:production.rb:
But only in production does reject_unauthorized_connection get returned because
request.params
is empty.Not sure if this is user error or a bug but it's very strange that this happens only on production. Is there anything that a production configuration could cause anycable to not parse request.params? Thanks!