Skip to content

fix: avoid duplicate Content-Type header in fetch402 #50

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
rolznz merged 1 commit into from
Jul 2, 2026
Merged

fix: avoid duplicate Content-Type header in fetch402 #50

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
15 changes: 11 additions & 4 deletions src/tools/lightning/fetch.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,10 +19,17 @@ export async function fetch402(client: NWCClient, params: Fetch402Params) {

if (method && method !== "GET" && method !== "HEAD") {
requestOptions.body = params.body;
requestOptions.headers = {
"Content-Type": "application/json",
...params.headers,
};
// A body is always passed as JSON, so default the Content-Type. The agent
// isn't required to set the header itself but might do so anyway, so only
// add our default when it's absent to avoid a duplicate Content-Type.
const headers = { ...params.headers };
const hasContentType = Object.keys(headers).some(
(key) => key.toLowerCase() === "content-type",
);
if (!hasContentType) {
headers["Content-Type"] = "application/json";
}
requestOptions.headers = headers;
} else if (params.headers) {
requestOptions.headers = params.headers;
}
Expand Down
Loading