You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a situation where I need to process a http request that uses a custom method (Blame Microsoft for abusing HTTP for RPC) I can handle with TemplatedApp<SSL>::any(...) to make sure a header with a cookie has specific data in it. If not I return a normal http response with unauthorized and the client can try again. If the cookie passes though it expects to upgrade to a websocket connection. I am sure I am missing something but from what I can tell TemplatedApp<SSL>::ws(...) only handles GET. Do I have to implement that same function with my custom method? Or is there an easier way?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I have a situation where I need to process a http request that uses a custom method (Blame Microsoft for abusing HTTP for RPC) I can handle with
TemplatedApp<SSL>::any(...)
to make sure a header with a cookie has specific data in it. If not I return a normal http response with unauthorized and the client can try again. If the cookie passes though it expects to upgrade to a websocket connection. I am sure I am missing something but from what I can tellTemplatedApp<SSL>::ws(...)
only handlesGET
. Do I have to implement that same function with my custom method? Or is there an easier way?Beta Was this translation helpful? Give feedback.
All reactions