[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2017-10-27 Thread Bug Watch Updater
Launchpad has imported 13 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=498884.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.


On 2009-05-04T09:13:11+00:00 Johan wrote:

Created attachment 342285
CUPS config

Description of problem:

When CUPS is accessed by host name, not localhost, access is rejected
and the message "Request from "localhost" using invalid Host: field
"fully.qualified.host.name:631""

This also makes printing from cups-friendly apps impossible.

Version-Release number of selected component (if applicable):

1.3.10-4.fc10 (updates-testing)
1.3.10-1.fc10 (updates)

How reproducible:

Always.

Steps to Reproduce (assuming the host has IP 192.168.1.251):

1. Using localhost:631, edit config -> choose default config
2. Enable
   - Share published printers connected to this system
   - Allow printing from the Internet
   - Allow remote administration
3. Save and restart cups
4. Access 127.0.0.1:631 -> works
5. Access 192.168.1.251:631 -> works
6. Access fully.qualified.host.name:631 -> "400 Bad Request"
  
Actual results:

6. Access fully.qualified.host.name:631 -> "400 Bad Request"

Expected results:

6. Access fully.qualified.host.name:631 -> works

Additional info:

cuspd.conf attached.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/0


On 2009-05-05T12:04:10+00:00 Tim wrote:

When you installed 1.3.10-4.fc10 from updates-testing it should have
adjusted /etc/cups/cupsd.conf to add "ServerAlias *" at the end.
However, your "step 1" above uses the upstream default configuration
(i.e. cupsd.conf.default) which does *not* have "ServerAlias *" at the
end, but should.

Fix coming shortly.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/1


On 2009-05-05T16:15:17+00:00 Johan wrote:

Thanks for the info. However, Adding "ServerAlias *" (and restarting CUPS) does 
not change anything for me.
The docs mention "If your CUPS server is accessed using a hostname or hostnames 
not known to the server itself you must add "ServerAlias hostname" to 
cupsd.conf for each such name." but I fail to see why CUPS does not know the 
FQDN of the local system. It's in /etc/hosts and DNS.
... Which precisely turned out to be the problem. The FQDN was stored in 
/etc/hosts as 127.0.0.1 and apparently CUPS doesn't like 2 IPs for a single 
FQDN.

AFAIC we can close this bug.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/2


On 2009-05-05T18:20:45+00:00 Tim wrote:

The question is: should we allow a request intended for a FQDN for this
host over the loopback interface?  Needs investigation and discussion
with upstream.

Reported upstream.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/3


On 2009-05-06T10:54:28+00:00 Tim wrote:

Intentional behaviour.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/4


On 2009-05-12T03:53:46+00:00 Fedora wrote:

cups-1.3.10-5.fc9 has been pushed to the Fedora 9 stable repository.  If
problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/5


On 2009-05-12T04:04:00+00:00 Fedora wrote:

cups-1.3.10-5.fc10 has been pushed to the Fedora 10 stable repository.
If problems still persist, please make note of it in this bug report.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/6


On 2009-06-25T08:29:57+00:00 Andrew wrote:

I confirm, that cups-1.3.10-5.fc10 runs well.
But cups-1.4-0.b2.18.f11 and 1.4-0.rc1.3.fc11 has the same or similar bug again.

Output after the remote access in my /var/log/cups/error_log of the
local machine:

E [22/Jun/2009:07:51:46 +0200] Request from "77.176.92.21" using invalid
Host: field "buero111.homelinux.net"

Output on the remote machine in /var/log/cups/error_log:
E [22/Jun/2009:07:52:13 +0200] [Job 357] Abfragen des Druckerstatus (Bad 
Request) nicht möglich!

(Translation: Request of printer status not possible)

buero111.homelinux.net is my dyn-DNS host name.

Reply at:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/comments/7


On 

[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2016-05-27 Thread Curtis Lee Bolin
** Changed in: cups (Ubuntu)
   Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/516018

Title:
  cups 400 Bad Request for fully qualified host name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2013-08-12 Thread Bug Watch Updater
** Changed in: cups (Debian)
   Status: New = Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/516018

Title:
  cups 400 Bad Request for fully qualified host name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2012-12-20 Thread sun
That's still open with Ubuntu Precise 12.04 LTS.
The fix described works for me.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/516018

Title:
  cups 400 Bad Request for fully qualified host name

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/516018/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2011-03-26 Thread Zero
Also I think this is important to support HOST.local
(avahi/bonjour/ZeroConf) type of name resolution.

I have a home network in wich i can't manage the routers dns since it
only relays a dns from the cloud and al machines are assigned via dhcp
so no static ips.

Avahi and Bonjour in Mac and Windows hosts have helped me to manage
internal names and services on my lan, having a server with a dynamic ip
is not ideal, but is the way It works better on the router side.

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/516018

Title:
  cups 400 Bad Request for fully qualified host name

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-10-23 Thread Scott Testerman
** Tags added: maverick

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-08-27 Thread Charlie Kravetz
 Thanks for reporting this bug and any supporting documentation. Since
this bug has enough information provided for a developer to begin work,
I'm going to mark it as confirmed and let them handle it from here.
Thanks for taking the time to make Ubuntu better!

** Changed in: cups (Ubuntu)
   Importance: Undecided = Low

** Changed in: cups (Ubuntu)
   Status: New = Triaged

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-07-25 Thread Jeremy Sargent
Hello,

I ran across this while having the same error. I'll add this info for
others to see...

It is best to use the ServerAlias directive with an actual hostname
versus the * command

Just add it to the end of the cupsd.conf file

Example: ServerAlias server-name.your-ip.com

Reason:http://www.cups.org/documentation.php/ref-cupsd-conf.html

Note

The ServerAlias directive is used for HTTP Host header validation
when clients connect to the scheduler from external interfaces. Using
the special name * can expose your system to known browser-based DNS
rebinding attacks, even when accessing sites through a firewall. If the
auto-discovery of alternate names does not work, we recommend listing
each alternate name with a ServerAlias directive instead of using *.

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-04-26 Thread Santi Reig Roman
Thank you very much Pretto, It works! You've saved my day!!

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-04-21 Thread Curtis Lee Bolin
Sorry, wrong tab

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-04-20 Thread Bug Watch Updater
** Changed in: cups (Debian)
   Status: Unknown = New

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-04-19 Thread Francesco Pretto
** Bug watch added: Debian Bug tracker #525910
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525910

** Also affects: cups (Debian) via
   http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=525910
   Importance: Unknown
   Status: Unknown

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-04-19 Thread Francesco Pretto
** Bug watch added: Red Hat Bugzilla #498884
   https://bugzilla.redhat.com/show_bug.cgi?id=498884

** Also affects: cups (Fedora) via
   https://bugzilla.redhat.com/show_bug.cgi?id=498884
   Importance: Unknown
   Status: Unknown

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-04-19 Thread Francesco Pretto
The solution seems to be add ServerAlias * to /etc/cups/cupsd.conf,
but it's not added automatically installing cups 1.4.3-1 in ubuntu
server 10.04 while it's there in ubuntu desktop 9.10.

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-04-19 Thread Curtis Lee Bolin
Adding ServerAlias * to /etc/cups/cupsd.conf did work.  Thank you,
Pretto, for you post.

This was missing from my Karmic server and Lucid test server.  This
small change has caused a huge problem.  This should either be well
documented or not removed from the default config file.

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-02-03 Thread Charlie Kravetz
** Tags added: karmic lucid

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs


[Bug 516018] Re: cups 400 Bad Request for fully qualified host name

2010-02-02 Thread Curtis Lee Bolin

** Attachment added: BootDmesg.txt
   http://launchpadlibrarian.net/38663654/BootDmesg.txt

** Attachment added: CupsErrorLog.txt
   http://launchpadlibrarian.net/38663655/CupsErrorLog.txt

** Attachment added: CurrentDmesg.txt
   http://launchpadlibrarian.net/38663656/CurrentDmesg.txt

** Attachment added: Dependencies.txt
   http://launchpadlibrarian.net/38663657/Dependencies.txt

** Attachment added: Locale.txt
   http://launchpadlibrarian.net/38663658/Locale.txt

** Attachment added: Lspci.txt
   http://launchpadlibrarian.net/38663659/Lspci.txt

** Attachment added: PrintingPackages.txt
   http://launchpadlibrarian.net/38663660/PrintingPackages.txt

** Attachment added: ProcCpuinfo.txt
   http://launchpadlibrarian.net/38663661/ProcCpuinfo.txt

** Attachment added: ProcInterrupts.txt
   http://launchpadlibrarian.net/38663662/ProcInterrupts.txt

** Attachment added: ProcModules.txt
   http://launchpadlibrarian.net/38663663/ProcModules.txt

** Attachment added: UdevDb.txt
   http://launchpadlibrarian.net/38663664/UdevDb.txt

** Attachment added: UdevLog.txt
   http://launchpadlibrarian.net/38663665/UdevLog.txt

-- 
cups 400 Bad Request for fully qualified host name
https://bugs.launchpad.net/bugs/516018
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs