SQL Editor UI for the http server plugin

[mishamsk]

Hey,

I've stumbled upon this issue from @lmangani - mattf96s/QuackDB#92

I am not sure if QuackDB ended up adding the feature, but my team and I created yet another (and arguably more advanced) browser-based DuckDB client https://github.com/pondpilot/pondpilot

We are actively developing it and looking to add more sources. Your http plugin seems like a great idea and something we want to add.

We'll probably add it to our roadmap and implement soon barring any technical issues (duckdb-wasm is pretty whimsical), but if there were any insights from QuckDB collaboration or anything you'd like to be included - would love feedback. We can discuss here, or you can open an issue in our repo or we feel free to shoot me an email.

Great work and community!

[lmangani]

Hello @mishamsk and thanks for opening this 👋
We'd love for http_server to become a datasource to your app of course - the barrier is pretty low as our API is loosely modeled after the ClickHouse HTTP API and its JSON format. Count on our help if you decide to proceed with it both in terms of adding features and/or support.

[mishamsk]

👍 sounds good. be on the lookout for the update. We are currently wrapping up a formal 0.2.0 update (although most features are already live) and we'll get to new data sources starting next week.

[mishamsk]

@lmangani created an issue - pondpilot/pondpilot#141 I'd love some feedback on the scope/design. I expect you to know more about real-life use cases, so I may be completely off

[booandrew]

@lmangani Hi! Quick update on PondPilot integration.

We've successfully implemented DuckDB HTTP Server support and it works great with no-auth connections. However, we discovered that authenticated connections fail from browsers due to CORS preflight issues.

The problem: When authentication is enabled, browser OPTIONS preflight requests get blocked with 401 Unauthorized, which prevents the actual authenticated request from going through. This affects any browser-based application trying to use authenticated connections to DuckDB HTTP Server.

Could you help us solve this CORS authentication issue?

Thanks! 👏🏻

[lmangani]

@booandrew indeed the order of Auth/CORS checks was generating this corner case. It should be fixed in this PR/branch: Query-farm/httpserver#44

UPDATE: v0.1.8 duckdb/community-extensions#506 ready to be published w/ the fixes

I'm excited about this integration and hope to see it on the PondPilot blog one day soon!

[lmangani]

@booandrew the changes have been merged. Could you retest w/ the latest httpserver version on DuckDB v1.3.2?

[booandrew]

Thank you! I'll test this implementation as soon as possible and report back with the results.
Really appreciate the quick response! ❤️

[booandrew]

Hi @lmangani!

Thanks for the CORS fix - it resolved the authentication issues perfectly!

While testing, I discovered that HTTP secrets work in native DuckDB but don't work in DuckDB WASM. The secrets are created successfully, but the authorization headers aren't attached to the actual HTTP requests, resulting in 401 errors

I tested this with:

• Native DuckDB 1.3.2 - works fine
• DuckDB WASM 1.29.1-dev269.0 - headers not sent

This appears to be a known WASM limitation (duckdb/duckdb-wasm#1967). Wanted to share this finding in case it helps others. Thanks again for your support!

[lmangani]

@booandrew thanks for the update! I was not aware of this WASM limitation but i'll investigate it and see what we can do there. If there's any other requirement for the integration, please fire up an issue and we'll do our best.