The initial HTTP request is immediately upgraded to a webscocket and after that all of Bokeh's communication happens over websocket. It might be possible to initiate a a websocket connection via POST (I don't happen to know offhand). But you are correct that in any case Bokeh simply does not support POST requests at present. You could file a Github feature request issue to investigate adding this, but I will be up front and state that there are many other priorities that would come ahead of this for the core team. Of course, we'd be happy to review and merge a Pull Request that adds this from a new contributor earlier.
Otherwise, the only other suggestion I have is that it might be possible to set up a proxy such as nginx in front of Bokeh somehow to make this work. But I am not certain that it is possible at all, and don't know how to do it in detail if it is.
Thanks for your explanation.
We were very confused about why bokeh serve do not support “POST”
before.
Regards,
Yolanda.
在 2018年5月23日星期三 UTC+8下午10:57:36,Bryan Van de ven写道:
···
Hi,
The initial HTTP request is immediately upgraded to a webscocket and after that all of Bokeh’s communication happens over websocket. It might be possible to initiate a a websocket connection via POST (I don’t happen to know offhand). But you are correct that in any case Bokeh simply does not support POST requests at present. You could file a Github feature request issue to investigate adding this, but I will be up front and state that there are many other priorities that would come ahead of this for the core team. Of course, we’d be happy to review and merge a Pull Request that adds this from a new contributor earlier.
Otherwise, the only other suggestion I have is that it might be possible to set up a proxy such as nginx in front of Bokeh somehow to make this work. But I am not certain that it is possible at all, and don’t know how to do it in detail if it is.