Skip to content

docs: clarify local HTTP transport limitation #10

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.

Sign up for GitHub

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

Merged
ChoMinGi merged 2 commits into from
Aug 6, 2026
Merged

docs: clarify local HTTP transport limitation #10

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
fc1ffe6
docs: clarify local HTTP transport limitation
ChoMinGi Jul 27, 2026
5c9ab68
Merge branch 'main' into agent/document-loopback-http-limit
ChoMinGi Aug 6, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -55,6 +55,11 @@ This quick start deliberately selects `standalone`, so the configured keys and h

Standalone endpoints must use HTTPS. For a loopback development receiver only, plaintext HTTP can be enabled explicitly with `langfuse.allow-insecure-http-for-development=true`; never use that option with production credentials.

That option only relaxes endpoint validation. Direct HTTP export to Langfuse Docker can currently
fail during cleartext HTTP negotiation with the JDK sender; use a local TLS reverse proxy or
HTTPS-capable collector until [#9](https://github.com/ChoMinGi/langfuse-otel-java/issues/9) is
resolved.

### Standalone (No Spring)

```xml
Expand Down