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
Currently the endpoint protocol is limited to "http", "ws", "tcp", "ws". This should be expanded to include "https" and "wss"
The description for the secure flag should be updated to make it clear that when it is set to true the protocol should be set to either https or wss.
Note also that parser documentation must make it clear that when the protocl is set, for example, to http, and the secure attribute is set to true it is the responsibilty of the consumer of the parser to convert http to https.
Currently the endpoint protocol is limited to "http", "ws", "tcp", "ws". This should be expanded to include "https" and "wss"
The description for the secure flag should be updated to make it clear that when it is set to true the protocol should be set to either https or wss.
Note also that parser documentation must make it clear that when the protocl is set, for example, to http, and the secure attribute is set to true it is the responsibilty of the consumer of the parser to convert http to https.
This was discussed in the dev file cabal on Nov 19th: https://docs.google.com/document/d/1Zn6D1gNu1gDidtillni0hNAeU5pscfqwhx4mv3MmmwY
The text was updated successfully, but these errors were encountered: