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 am having an issue where i use both REST and websockets in my server's API.
However (hence the title), only the initial HTTP GET route of the websocket (before the upgrade header is taken into account) is visible and some people mistake it for a regular REST route.
Is there a way using oatpp-swagger to document WS or WSS protocol's interface?
Kind regards,
Saadharta
The text was updated successfully, but these errors were encountered:
Hello there!
I am having an issue where i use both REST and websockets in my server's API.
However (hence the title), only the initial HTTP GET route of the websocket (before the upgrade header is taken into account) is visible and some people mistake it for a regular REST route.
Is there a way using oatpp-swagger to document WS or WSS protocol's interface?
Kind regards,
Saadharta
The text was updated successfully, but these errors were encountered: