Matt Godbolt

Good point! (wow, how big are your messages!) We should make this configurable though :)

Indeed! Seasocks started as a pure websockets-and-static-file system. But grew up...and ended up having much more sophisticated page handling. Eventually it would be nice to handle the file serving just...

Oh that's odd! I'll have to take a look. I use seasocks exclusively with chrome at work, and haven't seen this, but I don't doubt you. Will have a look...

Oh wow! I've never passed another parameter to new WebSocket; I'll use this knowledge to try and work out what's going on...

@malmut - did these update fix your issues?

@entrepidea does this answer your question? You can also try linking zlib statically, if disabling it isn't appropriate for you.

Hi there! When you do the `writer->header(...)` stuff, does the header actually make it into the header of the reply? Or does it appear in the body? You can test...

It actually looks like it's in there twice.... and yes, grepping the code we already put `Access-Control-Allow-Origin: *` in our messages! (Connection.cpp)...! So, as best I can tell the CORS...

Hi! Can you attach the packet capture itself instead of the text? It's much easier to debug in wireshark than in a text editor :) thanks!

ah! I was able to read enough: ``` Hypertext Transfer Protocol OPTIONS /system/serial-number HTTP/1.1\r\n Host: 192.168.137.138\r\n ``` is what was sent, which we don't support I think? Hard to tell