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’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[feat] access to URISchemeRequest
body on Linux
#666
Comments
Do we have an upstream issue to track it? |
I don't think we opened one for it yet. |
This is tricky to implement in WebKitGTK. There is no "request body" sitting around, it is a |
Let's expose that stream though, we actually care much more about that stream than a full body. Wry itself already has code to read a stream into a |
"Just expose a stream" still has complications. It is possible for a stream to be read-once. In which case you have to copy the entire thing into memory. It is also possible for a stream to be |
I am mostly thinking about this from a libsoup perspective, the http library webkitgtk uses, its possible things work out nicer inside of WebKit. |
Upstream issue created: https://bugs.webkit.org/show_bug.cgi?id=252564 |
seems like the upstream issue was fixed: WebKit/WebKit#10714 |
right, this has been implemented in wry behind |
Is your feature request related to a problem? Please describe.
Both the Rust type URISchemeRequest and upstream WebKitURISchemeRequest do not expose a way to access the requests body. For a variety of usecases including Tauri's IPC system it would be great if we could actually access the main content of the request.
Describe the solution you'd like
Implement this functionality in upstream projects mirroring the one from WKWebView URLRequest namely
httpBody
andhttpBodyStream
so we can consume the body both blocking and through a RustStream
.Describe alternatives you've considered
Not have access to the body on Linux and marking this as a platform difference, but sadly this is kind of a really important core feature. It being absent makes the custom protocol pretty useless.
Would you assign yourself to implement this feature?
Additional context
Add any other context or screenshots about the feature request here.
The text was updated successfully, but these errors were encountered: