fix: use fetch adapter for OPNsense 25.x compatibility#2
Open
cmatta wants to merge 1 commit into
Open
Conversation
OPNsense 25.x includes lighttpd 1.4.82 which has stricter HTTP header validation. The axios HTTP adapter sends headers that are rejected with "Invalid header received from client" (HTTP 400). The fetch adapter sends cleaner headers that pass validation. This is a one-line fix that makes the client compatible with both older OPNsense versions and 25.x+. See: https://www.lighttpd.net/2025/9/12/1.4.82/
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.
Addresses issue #1
Summary
Use axios fetch adapter instead of HTTP adapter to fix compatibility with OPNsense 25.x.
Problem
API requests fail with
HTTP 400: Invalid header received from clienton OPNsense 25.x due to stricter HTTP header validation in lighttpd 1.4.82+.Root Cause
OPNsense 25.x upgraded to lighttpd 1.4.82, which introduced stricter HTTP header validation:
The axios HTTP adapter (used by default in Node.js) sends headers that pass validation on older lighttpd versions but are rejected by lighttpd 1.4.82+.
The axios fetch adapter sends cleaner headers that pass the stricter validation.
Fix
Add
adapter: 'fetch'to the axios configuration insrc/http-client.ts.Impact
Testing
Tested against OPNsense 25.7.8 - all API calls now succeed.
Notes
NODE_TLS_REJECT_UNAUTHORIZED=0for self-signed certificates (thehttpsAgentoption doesn't apply to fetch)