Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

parse or map fragment from request URI #3716

Closed
tonytony2020 opened this issue Nov 3, 2023 · 1 comment
Closed

parse or map fragment from request URI #3716

tonytony2020 opened this issue Nov 3, 2023 · 1 comment

Comments

@tonytony2020
Copy link

tonytony2020 commented Nov 3, 2023

馃殌 Feature

Google's OAuth 2.0 APIs send callback request something looks like
GET https://some.service/callback/oauth/google#id_token=<...JWT...>&authuser=0&prompt=none

It's not possible implementation endpont for that callback handler parse id_token field value since grpc-gateway does not support parse or map fragment from request URI.

(A clear and concise description of what the feature is.)

Method parameters in the query string.

Any good idea?

@tonytony2020
Copy link
Author

When an agent (such as a web browser) requests a web resource from a web server, the agent sends the URI to the server, but does not send the fragment. Instead, the agent waits for the server to send the resource, and then the agent processes the resource according to the document type and fragment value.

https://en.wikipedia.org/wiki/URI_fragment#:~:text=When%20an%20agent%20(such%20as,document%20type%20and%20fragment%20value.

Ignore this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant