Feature Request: identify traffic from duckdb-wasm via request headers

[jdangerx]

We host some Parquet files in S3 that people access both through a browser-based tool built on duckdb-wasm as well as through direct link downloads and their own scripts.

We can get S3 access logs which show request headers like User-Agent, but all the browser-based requests are mixed together under similar User-Agents. It would be nice to identify how much traffic is coming from the tool vs. direct downloads!

I saw #1967, which is kind of related in that the user is trying to add custom headers (for authentication, not analytics purposes). If we could add extra headers like that, it would solve my problem... however it seems like that extra-header capability is part of the HTTPFS extension which is not supported in duckdb-wasm since duckdb-wasm is trapped inside the browser's HTTP stack.

We can certainly work around this issue - it's not critical - but it would be nice to be able to identify duckdb-wasm based traffic from S3 access logs, whether it's through setting custom headers, sending a new DuckDB-User-Agent header (as suggested in Discord), or some other creative solution!

[carlopi]

Answered at #2110