Trim whitespace from printhost API keys to avoid Prusa-Link HTTP 415 error#15448
Open
BasPaap wants to merge 1 commit into
Open
Trim whitespace from printhost API keys to avoid Prusa-Link HTTP 415 error#15448BasPaap wants to merge 1 commit into
BasPaap wants to merge 1 commit into
Conversation
…ilures. Pasted API keys can include trailing newlines that break X-Api-Key headers and cause misleading HTTP 415 errors from Prusa-Link. Co-authored-by: Cursor <cursoragent@cursor.com>
4 tasks
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
2 participants
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.
Summary
printhost_apikeywhen loading, editing, and saving Physical Printer settingsOctoPrintconstructor before sendingX-Api-Keyheaders (affects PrusaLink uploads)Problem
Copying the Prusa-Link API key into PrusaSlicer can include invisible trailing newline characters. Uploads then fail with a misleading
HTTP 415: Only G-Code for FDM printer can be uploadedeven though the G-code is valid. The web UI works because it uses digest auth instead of the API key.Related
Complements prusa3d/Prusa-Link#1047 (server-side API key sanitization).
Test plan