Listener fails on blob.

[disarticulate]

application/octet-stream are transmitted as binary blobs

also note:

• I'm not sure what the difference is between the passed in msgid and the regex being done to get the id
• Normal binary frames don't appear to work with bidirectional websockets. nginx appears to quash them. Except when I do (as stated in the docs):

  #!/usr/bin/python
  import requests
  res = requests.post(url='http://localhost/is/'+endpoint,
                  data=image,
                  headers={
                      'Content-Type': 'application/octet-stream'
                  })

  which makes it pretty useless as content-type isn't transferred.

[slact]

This is the intended behavior:

Messages are delivered to subscribers in text websocket frames, except if a message's content-type is "application/octet-stream" -- then it is delivered in a binary frame.

see https://nchan.io/#websocket

[disarticulate]

The intention is not to process blobs?

On Sat, Mar 31, 2018, 7:53 PM slact notifications@github.com wrote:

This is the intended behavior:

Messages are delivered to subscribers in text websocket frames, except if a message's content-type is "application/octet-stream" -- then it is delivered in a binary frame.

see https://nchan.io/#websocket

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/slact/nchan.js/pull/15#issuecomment-377734385, or mute the thread https://github.com/notifications/unsubscribe-auth/AQp7PeuSiT8BbpfgUtlFnrkZAIr-pt4Cks5tkCUlgaJpZM4TCf5G .

[slact]

err, the content-type behavior is as intended.

Your Blob fix was the right approach, but it needed a little more massaging. Thanks for the PR, i'll release this version on npm in a few days.

[disarticulate]

I guess my point was that you can't send binary frames via the websocket. I was aware that you can send binary data to the POST channel.

Is there a technical reason not to let websockets send binary messages?

[slact]

You can send binary frames via websocket by adding add_header "Content-Type" "application/octet-stream"; to your nginx publisher location. There is no way to conditionally send binary blobs over websocket for a given URL.