ianc
I want to disable websockets in my browser (e.g Chrome, Firefox, etc) to experience the JS fallback (longPoll) in my LiveView application.
You think it would be simple to turn off websockets somewhere, but it’s not!
Note that I don’t want to “hack” the fallback in app.js by altering longpollFallbackMs or similar approaches. I want to experience the fallback as a user would if their network connection blocks websockets.
Thanks for any suggestions and hopefully I’ve just overlooked something.
Where Next?
Trending in Questions
Other Trending Topics
Latest Phoenix Threads
Latest on Elixir Forum
Sponsor Spotlight
Build Elixir applications with speed and confidence.
Categories:
Sub Categories:
Forums
Popular Tags
- #ecto
- #liveview
- #troubleshooting
- #learning-elixir
- #library
- #deployment
- #erlang
- #testing
- #genserver
- #mix
- #absinthe
- #remote-other
- #otp
- #plug
- #how-to-question
- #macros
- #postgres
- #elixirconf
- #channels
- #exunit
- #discussion
- #code-sync
- #podcasts
- #javascript
- #onsite
- #dialyzer
- #docker
- #authentication
- #umbrella
- #full-time-contract
- #podcasts-by-brainlid
- #ai
- #ecto-query
- #elixirconf-us
- #blog-post
- #elixir-ls
- #phoenix_html
- #iex
- #graphql
- #genstage
- #websockets
- #supervisor
- #advent-of-code
- #distillery
- #processes
- #elixirconf-eu
- #api
- #forms
- #metaprogramming
- #hex
Our Sponsors
Supporting innovation across the BEAM ecosystem.
We build reliable cloud platforms for business-critical systems.
Catch errors, track performance, monitor hosts and more.
Error tracking, logs, uptime, and Just Enough APM. Built for developers.
Elixir, Erlang & BEAM conferences from Code Sync - join us in 2026!
Master modern tools, write cleaner code, and tackle real-world challenges.
Bringing learning, work and compliance together since 1987.
The deployment platform built for Elixir: PaaS ease, VPS control.
The team behind Membrane, Popcorn, LiveDebugger. Available for hire.
Courses that'll move you from confusion to "Aha, now I get it!"
Showing Posts 1 to 8- Show Best Posts
- Show All (oldest first)
- Show All (newest first)
ErikNaslund
Would it work for you if you blocked requests to a specific URL or URL pattern?
If that’s the case, then you can simply right click a URL in the “Network” tab of the Chrome dev tools and select “Block request URL”.
You can also add URLs and URL patterns manually on the “Network request blocking” tab.
ianc
I hadn’t tried that… but it doesn’t seem to work.
After blocking the socket URL, it still seems to send messages over it.
Update: I also tried adding wildcards to block the socket URL, to no avail.
ErikNaslund
My bad. A quickly googling suggest that this option only blocks requests like those done with
XMLHttpRequestorfetch.Using an extension like https://chromewebstore.google.com/detail/url-blocker/jpakadanffilpnjijlmmkljogkfaognd does seem to work (I just tested it). It’s not nearly as nice to work with, and that particular extension might not be allowed by Chrome for much longer…but it works for now, and maybe there’s a nicer extension out there which you could make use of.
ianc
Thanks for taking a look!
I can’t get that extension working. I set up a regex to block the websocket, but when I reload the page with the extension enabled, the WS continues to pass messages when I inspect the payloads.
ErikNaslund
Hmm, how weird.
I actually did get it to block the WS connection using that extension (it showed as blocked in the dev tools, and the app reacted to it)…but now that I’m trying again I can’t get it to work either
ianc
Perhaps there’s a way to get Bandit to block websockets? It’s interesting how difficult it is!
ErikNaslund
Like, you could always comment out the
. I feel I’m treading a bit into “I don’t want to “hack” the fallback” territory here though.
socket "/live"from yourendpoint.ex, or make a plug that refuses the connection…then you definitely won’t get any ws connectionsbokiro
I also looked for options to block the creation of a websocket connection for my project. I did not find anything suitable. The most convenient way for me was to use the DevTools “override” tool. I changed the JS-file in terms of creating a websocket connection.