wasm: use browser HTTP bridge for static httpfs - #546
Merged
Conversation
adsharma
changed the title
adsharma
force-pushed
the
fix_wasm_build
branch
2 times, most recently
from
June 1, 2026 23:51
c3d73b4 to
eec1cb1
Compare
adsharma
marked this pull request as ready for review
June 2, 2026 01:51
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Notes
The browser path mirrors DuckDB's wasm approach by issuing browser-managed HTTP requests from the wasm build instead of trying to use OpenSSL sockets. This avoids BIO_new_socket and OPENSSL_NO_SOCK issues in wasm.
Validation