Re: Request header in response

Okay, for this you just need a unique identifier for the message. e.g.
one header "Message-Id: 12345"  in the request and response.

Am 15.11.2015 um 20:50 schrieb Dave Wain:
> But to match the response to the request requires (some of) the request
> header to be part of the response header.
>
> For example, if requests go via a satellite phone but the response comes
> via a satellite broadcast channel, there would be no way to de-multiplex
> the responses.
>
> Regards
> Dave
>
> -----Original Message-----
> Sent: 15 November 2015 16:18
> To: dave.wain@ntlworld.com
> Cc: ietf-http-wg@w3.org
> Subject: Re: Request header in response
>
> Hello Dave,
>
> I would like to understand in which way you think that HTTP depends on
> TCP/IP and how it wouldn't if the response contains the request headers?
> IMHO the underlying communication protocol has nothing to do with it.
> As long as you can parse the message syntax and make the connection
> management you are independent of the underlying transport layer:
> You could even transfer HTTP messages via UDP, UNIX sockets (as I sometimes
> do), or whatever you want.
>
> Am 15.11.2015 um 06:05 schrieb Dave Wain:
>> Dear All,
>>
>> If the request header (or most of it) is included in the response 
>> header, HTTP would become its own transport layer, independent of 
>> TCP/IP.
>>
>> This would be especially useful for remote locations.
>>
>> DW
>>
>> Note: This message is private and confidential and hence must be 
>> received without interception or distortion by the intended recipients 
>> only. Permission to use the information explicitly must come from the 
>> sender (and recipients).
>>
>> My personal web site and alternate contact details are at:
>> http://homepage.ntlworld.com/dave.wain/.
>>
>>
>>
>>
>>

Received on Sunday, 15 November 2015 20:00:27 UTC