Bug#952894: cups: Bad Request for FQDN without explicit ServerAlias

2020-03-02 Thread Kevin Locke
On Mon, 2020-03-02 at 08:48 +0100, Didier 'OdyX' Raboud wrote: > Le dimanche, 1 mars 2020, 16.43:56 h CET Kevin Locke a écrit : >> Accessing CUPS via https://hostname:631 works while >> https://hostname.example.com:631 fails with 400 Bad Request if >> cupsd.conf does not contain either "HostNameLoo

Bug#952894: cups: Bad Request for FQDN without explicit ServerAlias

2020-03-01 Thread Didier 'OdyX' Raboud
Le dimanche, 1 mars 2020, 16.43:56 h CET Kevin Locke a écrit : > Accessing CUPS via https://hostname:631 works while > https://hostname.example.com:631 fails with 400 Bad Request if > cupsd.conf does not contain either "HostNameLookups on" or > "ServerAlias printserver.example.com". This is a dive

Bug#952894: cups: Bad Request for FQDN without explicit ServerAlias

2020-03-01 Thread Kevin Locke
Package: cups Version: 2.3.1-7 Severity: normal Dear Maintainer, Accessing CUPS via https://hostname:631 works while https://hostname.example.com:631 fails with 400 Bad Request if cupsd.conf does not contain either "HostNameLookups on" or "ServerAlias printserver.example.com". This is a divergen