Skip to content

Conversation

@Hector-Work
Copy link

Removed the hardcoded HTTP scheme and port to allow the user to decide what they want to use. Currently, HTTPS URIs are changed to HTTP, which can prevent communication with the printer.

Recently experienced this on a Windows Print Server where SSL was required. Took a while to work out why the request was failing, but eventually found the scheme hardcoded in the library. Removing it allowed me to specify HTTPS in the server's address.

… decide what they want to use. Currently, HTTPS URIs are changed to HTTP, which can prevent communication with the printer.
This was referenced Dec 11, 2023
@danielklecha
Copy link

It appears that this repository is currently no longer actively maintained. However, the requested fix (along with several other improvements) is now available in an actively maintained fork: SharpIppNext.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants