'Bug#44665: How did you configure the CUPS server?'

[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    Bug#44665: How did you configure the CUPS server?
From:       Martin Kiehne <martin.kiehne () tu-clausthal ! de>
Date:       2002-07-31 13:29:16
[Download RAW message or body]

Hi Michael,

thanks for replying so soon, and sorry for me being a little bit late.

> I can try to find a better solution, but first of all, I need at least
> to reproduce it, which I can't. How did you disable the classes? I
> tried locally by adding:
>
> <Location /classes>
> Order Deny,Allow
> Deny From All
> </Location>
This is exactly what is causing the effect for us.
I suppose you tried accessing /classes/ via a web browser and got 
403 Forbidden?

Here's a dump of the communication between kprinter and our cups server (I 
removed the content data because it contains non-printable characters, except 
for the last reply):
===========================================================
POST /printers/ HTTP/1.1
Content-Length: 224
Content-Type: application/ipp
Host: localhost

[data...]
-----------------------------------------------------------
HTTP/1.1 200 OK
Date: Wed, 31 Jul 2002 12:56:31 GMT
Server: CUPS/1.1
Connection: Keep-Alive
Keep-Alive: timeout=60
Content-Language: C
Content-Type: application/ipp; charset=iso-8859-1
Content-Length: 4795

[data...]
-----------------------------------------------------------
POST /classes/ HTTP/1.1
Content-Length: 224
Content-Type: application/ipp
Host: localhost

[data...]
-----------------------------------------------------------
HTTP/1.1 403 Forbidden
Date: Wed, 31 Jul 2002 12:56:31 GMT
Server: CUPS/1.1
Content-Language: C
Upgrade: TLS/1.0,HTTP/1.1
Connection: close
Content-Type: text/html
Content-Length: 150

<HTML><HEAD><TITLE>403 Forbidden</TITLE></HEAD><BODY><H1>Forbidden</H1>You 
don't have permission to access the resource on this server.
===========================================================

Note:
"Host: localhost" in the POST request is not quite true though. In order to 
capture the communication I hacked jumpgate to dump the traffic while 
forwarding it from localhost to our server, and directed kprinter to the 
localhost. Anyway, the behaviour of kprinter is the same as if it connects 
directly to the server, so I think it doesn't do any harm.

Hope this helps.

Thanks,
Martin

(Complete bug history is available at http://bugs.kde.org/db/44/44665.html)
[prev in list] [next in list] [prev in thread] [next in thread]
Configure | About | News | Add a list | Sponsored by KoreLogic