Prev: wpa supplicant
Next: Need to keep a more robust DNS cache in my Windows client
From: Bob Tennent on 18 Jan 2010 15:16
On Mon, 18 Jan 2010 20:49:34 +0100, Pascal Hambourg wrote:
> Bob Tennent a �crit :
>> >
>> > Did you achieve a complete HTTP transaction or just the TCP connection ?
>>
>> How do I do that?
>
> To get <http://www.example.com/path/to/document> :
>
> GET /path/to/document HTTP/1.1
> Host : www.example.com
>
> Then press enter again to add an empty line.

I then get

<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>400 Bad Request</title>
</head><body>
<h1>Bad Request</h1>
<p>Your browser sent a request that this server could not understand.<br />
</p>
<hr>

etc.

>> If I enter q (I was trying to quit!), I get a dump of index.html.
>
> The real index.html or a page containing an error message such as
> "Method not implemented" ?

The real index.html.

> Anyway, if you got some HTML from the server then I guess it counts as a
> transaction.
From: Bob Tennent on 18 Jan 2010 19:52
On Mon, 18 Jan 2010 14:03:05 +0000 (UTC), Bob Tennent wrote:
> When I try to do a yum update on a Fedora 11 system, I'm getting strange
> messages:
>
> http://dl.atrpms.net/f11-i386/atrpms/stable/repodata/repomd.xml: [Errno 4]
> IOError: <urlopen error [Errno -2] Name or service not known>
>
> Another symptom is that Firefox produces
>
> Server not found
>
> Firefox can't find the server at www.google.com
>
> *unless* I use privoxy as a local proxy. Opera seems to be unaffected
> but konqueror produces
>
> Cannot talk to klauncher: Not connected to D-Bus server.
>
> The program on your computer which provides access to the http
> protocol could not be started. This is usually due to technical reasons.
>
> A third symptom that might be relevant is the following system message:
>
> localhost pulseaudio[4068]: main.c: Unable to contact D-Bus:
> org.freedesktop.DBus.Error.NoServer:
> Failed to connect to socket /tmp/dbus-m7qkzT4Q7E: Connection refused
>
> Can anybody explain what has happened?

I still don't know what happened, but a restart of iptables (i.e., the
firewall) seems to have fixed the problem, though why an earlier re-boot
did *not* is a mystery. I can now use yum and firefox without privoxy,
and I'm no longer getting system-log messages from pulseaudio.

Bob T.
First  |  Prev  | 
Pages: 1 2 3
Prev: wpa supplicant
Next: Need to keep a more robust DNS cache in my Windows client