Improve IPP diagnostics for Epson issue #75 - #90
Merged
Conversation
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
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
windows_ipp_probe.pyto v2.4--diagnosemode that sends read-only Get-Printer-Attributes requests--diagnoseis requestedWhy
Issue #75 currently reduces the Epson XP-345 response to:
That does not distinguish a wrong path, redirect, HTML error page, empty HTTP response, IPP version rejection, or a real malformed IPP reply. This diagnostic output should tell us which one it is before changing MintPRINT's Amiga-side query logic.
Test command for #75
Please attach the complete output, including the endpoint/version diagnostics section.