Can not get http header info from a Phoenix socket. %Phoenix.Socket{ assigns: %{}, channel: nil, channel_pid: nil, endpoint: Web.Endpoint, handler: Web.UserSocket, id: nil, join_ref: nil, joined: false, private: %{}, pubsub_server: App.PubSub, ref: nil, serializer: Phoenix.S…

Also don’t forget to actually enable sending those headers by configuring your socket on your Endpoint correctly as described here: Phoenix.Endpoint — Phoenix v1.8.8 So your Endpoint socket declaration should look like something like this: # inside the file lib/my_app_web/endpoint.ex # socket "/so…

:waving_hand: There is also connect_info passed as an optional third argument to connect/3 callback, it might be worth checking for headers there. def connect(params, socket, _connect_info) do {:ok, assign(socket, :user_id, params["user_id"])} end

Thank you two, I got it. :smile:

[image] rjk: So your Endpoint socket declaration should look like something like this: # inside the file lib/my_app_web/endpoint.ex # socket "/socket", MyAppWeb.UserSocket, websocket: [ connect_info: [:peer_data, :x_headers, :uri] ] Now you should see those headers being forwarded insi…

There is not. The available options are listed here: Phoenix.Endpoint — Phoenix v1.8.8

If you really wanted I think you could selectively rewrite/duplicate the headers you want to x_some_header format so you can access them via x_headers. Could be possible via a plug that’s running before the socket endpoint, otherwise it should be possible with a Cowboy handler, last resort that shou…

[image] rjk: Are you able to share you existing use case? Just curious and maybe there’s another solution for it. I am writing an Elixir Quickstart for a Thrird Party integration in any Elixir API serving mobile apps, and I need to check that the Third Party JWT token is valid in the request …

I have an API product in production that authenticates JWT tokens on the phoenix socket ‘connect’. But the token comes in through query params, you can’t use that way also?

There’s a reason for the options to be as restricted as they are: Phoenix channels are meant to be transport agnostic. The more implementation details surface into the actual channels system the more it becomes impossible to switch out transports transparently. So details are kept intentionally limi…

Thinking about it, what you could also try if you still want to use the JWT token from the header, is to make a HTTP route that you land on as a user, authenticates the JWT and redirects to the socket path but this time with a phoenix token inside the query params. So instead of doing a GET on the s…

[image] LostKobrakai: There’s a reason for the options to be as restricted as they are: Phoenix channels are meant to be transport agnostic. The more implementation details surface into the actual channels system the more it becomes impossible to switch out transports transparently. So details a…

Elixir Programming Language Forum

How to access http headers in Phoenix socket?

Questions & Help Questions

gsmlg June 9, 2020, 3:01am 4

Thank you two, I got it.