Skip to content
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.

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

When I start with print wizard unencrypted, all input gets lost when web interface switches to encrypted #1592

michaelrsweet opened this issue Apr 23, 2006 · 1 comment


Copy link

@michaelrsweet michaelrsweet commented Apr 23, 2006

Version: 1.2-current User: till.kamppeter

If I allow remote administration on a CUPS server and start the server's web interface with


from a remote machine, then click the "Administration" tab and start adding a new printer by clicking one of the "Add printer" (manual setup) or "Add this printer" (automatic setup of auto-detected printer) I get into the Add Printer Wizard and all data is entered unencrypted (still on "http://..."). In the end, when the queue gets actually added, CUPS switches to SSL and shows an "Upgrade required" message, but instead of then being asked for the password in SSL mode, I get directed to


and have to do all steps of the Add Printer Wizard again, this time in SSL mode.

What I expect:


make the web interface auto-upgrading to SSL before the wizard begins


let it auto-upgrading to the step where I am (which would mean that in the end of the wizard the "Upgrade required" message appears and then the password dialog fires up and after entering the password I get confirmation that the queue is set up).

I prefer the first of the two, as if the URI contains a password (eg: smb://user:password@winserver/share/) the whole wizard always running in SSL mode protects the password in the URI.

Copy link
Collaborator Author

@michaelrsweet michaelrsweet commented Apr 23, 2006 User: mike

We can't do #2 since you can't redirect POST's.

I've updated the default cupsd.conf to add an Encryption Required line to the /admin location when SSL is available - that will achieve #1.

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

No branches or pull requests

1 participant