jkarneges on master
fix parsing of ports without an… (compare)
jkarneges on master
Improve port parsing in pushpin… Merge pull request #47707 from … (compare)
jkarneges on master
proxy: eat Pushpin-Route header (compare)
jkarneges on v1.35.0
jkarneges on master
update version update dev version (compare)
jkarneges on master
be explicit (compare)
jkarneges on master
add local_ports option (compare)
jkarneges on master
fix for unix sockets with relat… add prometheus_prefix option (compare)
jkarneges on master
simplehttpserver: ability to li… statsmanager: ability to listen… (compare)
jkarneges on master
ensure pushpin-publish stays ex… (compare)
jkarneges on master
add requests received metric (compare)
jkarneges on master
only log route if explicitly set (compare)
jkarneges on master
move simplehttpserver into core… statsmanager: maintain combined… statsmanager: add prometheus se… and 4 more (compare)
jkarneges on master
add no_grip route condition par… (compare)
jkarneges on master
ensure each route has an ID, ev… if a route ID is shared and thu… use the route of the initial re… and 1 more (compare)
jkarneges on routeheader
jkarneges on master
update routesfile tests (compare)
jkarneges on master
routesfile: move empty initial … use QMultiHash domainmap: add mode to look up … and 3 more (compare)
jkarneges on routeheader
routesfile: move empty initial … use QMultiHash domainmap: add mode to look up … and 3 more (compare)
jkarneges on master
runner: allow `:0` as a valid l… Merge pull request #47706 from … (compare)
nc -l {port}
and make a non-ssl request to it on localhost. there are only a few ways that error message can happen, and it should be clear from the request what is causing it
Hi @jkarneges. I'm trying to replicate examples from the Quickstart guide for Websockets-Over HTTP.
Initial connect and echo work, but pushpin drops the connection in 8-10 seconds.
I noticed one error message in pushpin logs "[DEBUG] 2022-04-22 13:07:09.981 [proxy] wsproxysession: 0x6000032e8680 wscontrol session error
"
Here's my sinatra backend:
require 'sinatra'
post '/stream' do
status 200
data = request.body.read
if !data.index("OPEN").nil?
headers(
'Content-Type' => 'application/websocket-events',
'Sec-WebSocket-Extensions' => 'grip; message-prefix=""'
)
c = 'c:{"type": "subscribe", "channel": "mychannel"}'
body "OPEN\r\nTEXT 2F\r\nc:#{c}\r\n"
else
headers('Content-Type' => 'application/websocket-events')
body data
end
end
pushpin version: 1.35.0
I'm connecting with "wscat", but it seems the same result is with curl or normal websocket clients
Any ideas?
Ok. I found the issue in my code. The grip control message was not correctly formed: I included "c:" two times by mistake.
Btw, pushpin logs pointed me to the right direction with this log entry:
[DEBUG] 2022-04-22 16:23:50.306 [handler] grip control message is not valid json
I may need look into gripcontrol gem again. That should help avoid such silly mistakes going forward.
prometheus_port
setting (see https://pushpin.org/docs/configuration/#pushpinconf-file). it provides aggregate values similar to the report
event