phtrivier
I’m using phoenix 1.3.2
I have a socket that checks for user authentication at connection time:
def Socket do
use Phoenix.Socket
def connect(params, socket) do
case check_authentication_params(params) do
{:ok, authed_socket} -> {:ok, authed_socket}
_ -> :error
end
end
end
I connect in a browser with the phoenix npm package:
import { Socket } from 'phoenix';
let webSocket = new Socket(`....`);
webSocket.onError(error => {
// Handle error
});
webSocket.connect()
My problem is that, on the client side, in the webSocke.onError handler, the error event seems to be the same when:
- the connect succeeds, but later the connection is dropped (momentarily, for example, when my server restarts)
- the connection is done with wrong params, so the
connectfunction returns :error. I have log line that says:
WebSocket connection to '....t?vsn=2.0.0' failed: Error during WebSocket handshake: Unexpected response code: 403
But I cannot make the difference in the code.
What I want to do is to forcefully disconnect the websocket (to avoid repeated reconnection attempt) when I know the client does not have the proper credentials.
If I always use webSocket.disconnect in the error handler, then, as I understand it, I loose automatic reconnection in case of a network hicup.
Is there a way around that ?
Trending in Questions
Hello!
Suppose you are building workflow (order / task / payment) processing system with the following requirements:
Each workflow con...
New
Hey guys,
I’ve got a huge CSV ( around 10 GB ) that needs to be processed hourly
Do you guys have any suggestions what is the best prac...
New
Hello!
Could someone please give me a help/sample code, how to delete a file from s3 using waffle/waffle_ecto from Phoenix app.
I creat...
New
I have what I’ve heard referred to as a “lookup table” in my database. This is a way of assigning codes to common values. One common lo...
New
Hello,
I’m developing a online persistent chat system (what’s app) like using elixir/dynamodb/aws for a mobile app(flutter).
The diffic...
New
What approach to take when sending live updates to “random” users Hi! I have a question, I have a little chat app, and when I create a DM...
New
I think I’ve found a small improvement I could contribute to <%= web_namespace %>.CoreComponents (installer/templates/phx_web/compo...
New
Other Trending Topics
Hobbes is a low-level distributed database for the Elixir programming language.
Hobbes provides a simple, safe, and scalable storage lay...
New
ExRatatui lets you cook up rich terminal UIs in Elixir, powered by Rust’s ratatui via Rustler NIFs. Build interactive terminal applicatio...
New
Hello everyone. After busy few months I am happy to announce v0.1.0 of Emerge & Solve.
They are GUI (Emerge) and State management (S...
New
Corex is an accessible, unstyled UI component library for Phoenix that integrates Zag.js state machines using Vanilla JavaScript and Live...
New
There are three potential reasons for members of this forum to have a look at https://vutuv.de
You are tired or annoyed of LinkedIn.
Yo...
New
ICal is a library for interacting with iCalendar data. It parses iCalendars into typed Elixir structs via ICal.from_ics, and can prepare ...
New
Latest Phoenix Threads
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #deployment
- #library
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #javascript
- #podcasts
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ecto-query
- #elixir-ls
- #blog-post
- #ai
- #phoenix_html
- #elixirconf-us
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #api
- #forms
- #hex
- #security
- #metaprogramming









