No, Bokeh server apps only have access to URL parameters, e.g ?foo=10, etc. Unfortunately sending the full HTTP request is not compatible with --num-procs or with running multiple servers behind a load balancer, because the process that gets the initial request is not guaranteed to be the same process that actually runs the app code. You can see the lengthy discussion here:
There is an open issue to improve possibilities for Bokeh to preserve state across different workers:
I outlined a generic, policy-based mechanism that would let users choose how state is shared, and not impose any specific requirements. I think that is the best approach, and I'd be happy to help anyone that wants to work on it get started.
On May 25, 2018, at 02:02, yolanda chen <[email protected]> wrote:
I need to send a parameter to bokeh serve on header as this parameter is very long (7000+ byte). Can bokeh serve get the parameter on HTTP header? I tried to send a HTTP request with a parameter on header to bokeh serve and get the parameter by "curdoc().session_context.request.arguments", nothing was found.
You received this message because you are subscribed to the Google Groups "Bokeh Discussion - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/bokeh/9c21a1c8-b37e-42e0-9380-842fcf7fe4a1%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.