The Socket page supports needAuth as true #97
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When GetServer sets WebSocket's GetPage to
needAuth: true
, JWT authentication will fail and a prompt of "Invalid JWT token!" will be thrown.Because the Flutter client's GetSocket can only set the url parameter, there is no place to set other headers.
The websocket implementation of the dart language can support adding userInfo as authentication information in the url parameter,
It's just that the authentication information starts with Basic instead of JWT's Bearer.
Therefore, this modification changed GetServer to add checks for Basic authentication information. Although this Basic information is a JWT authentication Token, this is the minimum modification.
The modifications include: