Re: HTTP Request Forwarding?

in your scenario the underlying TCP protocol doesn't allow server C to 
reply to A on the existing connection between A and B.

if you wanted A to think the resource from C is really coming from B, 
then B would need to proxy the request through to C, and forward the 
response back through its connection.

if the HTML resource contained image tags on a different server that 
server B really wanted A to ask it for instead, it would need to 
re-write the HTML that was being sent back to the client.

this is how CGI proxies work for instance, they re-write the content 
passing through them so that subsequent requests (anchor and image tags) 
come back through them.

I'm sure there are some special cases that don't work with this approach.

Adrien


Mike Schinkel wrote:
> Hi all:
>
> I notice renewed activity on the HTTP spec and thought I would ask about
> what I would call "HTTP Request Forwarding."  As far as I know HTTP doesn't
> support (but I sure would be glad to found out I misread the specs, if I
> did!).  I wrote a blog post describing it and giving a use-case at [1].
>
> Basically, what I'm asking is:
>
> 1.) Did I misread the spec, and HTTP Request Forwarding actually is
> offered?, and 
>
> 2.) If Request Forwarding is not currently part of the HTTP spec are there
> any potential security issues that would make adding it impossible?, and 
>
> 3.) Is it possible to discuss including Request Forwarding init the HTTP
> spec?
>
> BTW, I posted to both www-talk@w3.org and ietf-http-wg@w3.org because I
> didn't know where was appropriate; if someone can direct me to the list that
> is most appropriate of the two I'd appreciate it. 
>
> Thanks in advance.
>
>

Received on Thursday, 8 March 2007 05:27:39 UTC