Shawn Holwegner wrote:
>
> The most common form of Request-URI is that used to identify a
> resource on an origin server or gateway. In this case the absolute
> path of the URI MUST be transmitted (see section 3.2.1, abs_path) as
> the Request-URI, and the network location of the URI (authority) MUST
> be transmitted in a Host header field. For example, a client wishing
> to retrieve the resource above directly from the origin server would
> create a TCP connection to port 80 of the host "www.w3.org" and send
> the lines:
>
> GET /pub/WWW/TheProject.html HTTP/1.1
> Host: www.w3.org
So if I can connect to server X and retrieve pages from server A on a
completely unrelated network, does this indicate an overly lax
configuration?
eg:
casper@casper:~$ nc www.serviceX.com 80
GET / HTTP/1.1
Host: www.serviceA.com
Txs,
--
Casper Boden-Cummins
The only war that matters is the war against the imagination
- Diane diPrima
S/MIME Cryptographic Signature
