You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I add a new printer via the "Add Printer" button in the web interface and enter as queue name a string of onluy digits, like 1111, 12345, ... I always get the response that a printer with this name already exists, independent which sequence of digits I choose.
If for some reason such names cause problems, for example for CUPS picking up this printer as temporary queue, or generally for IPP clients, and therefore such a name is not allowed, please let PAPPL respond with a decent error message (like "Printer name has to contain at least one letter" or similar).
The text was updated successfully, but these errors were encountered:
The issue is that /ipp/print/NNN gets recognized as a job ID for the default printer. I'll update the code to require a printer name that starts with a non-digit.
OK, so I've updated papplPrinterCreate to sanitize the resource path (not just a straight /ipp/printer/printer-name) so that you can still specify any arbitrary string (still needs to be valid Network Unicode UTF-8 per STD 92).
[master aba1f90] Fix adding of printers whose names contain special characters (Issue #161)
[v1.0.x 75824e9] Fix adding of printers whose names contain special characters (Issue #161)
If I add a new printer via the "Add Printer" button in the web interface and enter as queue name a string of onluy digits, like 1111, 12345, ... I always get the response that a printer with this name already exists, independent which sequence of digits I choose.
If for some reason such names cause problems, for example for CUPS picking up this printer as temporary queue, or generally for IPP clients, and therefore such a name is not allowed, please let PAPPL respond with a decent error message (like "Printer name has to contain at least one letter" or similar).
The text was updated successfully, but these errors were encountered: