Adding a protocol header to Laravel Reverb | Laravel | Page 1

gritty ingot Jul 17, 2024, 12:40 PM

#

I am currently working on a system that connects with Electric Vehicle chargers to process data of charge sessions, connector status, etc. This communication is done using OCPP, which is a standardized set of calls over websockets.

In the past, we used the laravel-websockets package to handle the communication, but since this is no longer supported, we would like to switch to Laravel Reverb instead. However, the OCPP standard requires us to add a Sec-Websocket-Protocol = ocpp1.6 header to our application's websockets. And by doing so, we get an error back stating Could not connect to server: Server sent no subprotocol.

So far, we haven't been able to find a way to tell Reverb to add this header, and I was wondering if someone here would be able to point me into the right direction.

dry igloo Jul 18, 2024, 7:57 AM

#

Sorry, I have no clue, but it sounds interesting. Mind sharing how it works? I mean just the basic flow.

gritty ingot Jul 18, 2024, 9:15 AM

#

@dry igloo in what sense? You mean like why we need this header and how it should be implemented?

dry igloo Jul 18, 2024, 10:27 AM

#

gritty ingot <@606095298821095434> in what sense? You mean like why we need this header and h...

I'm just curious where the connection to the charger is initiated from, and how the backend receives events from the charger. Because I'm only familiar with websocket connections initiated from a browser.

#Adding a protocol header to Laravel Reverb