- From: Peter Lepeska <bizzbyster@gmail.com>
- Date: Fri, 4 May 2012 16:15:52 -0400
- To: Andreas Petersson <andreas@sbin.se>
- Cc: ietf-http-wg@w3.org
- Message-ID: <CANmPAYHS_aKK0=VnKFRsD8qVXw0M4dHZic1xDDLVa7vLXCwftw@mail.gmail.com>
I can think of an enterprise use case but it's pretty contrived. WAN optimizing appliances use the TCP option field to auto-negotiate optimized connections when appliances are present in the data path. See http://www.cisco.com/en/US/docs/solutions/Enterprise/Data_Center/WAASDC11.html . Should there be an HTTP proxy in between those optimizing appliances, the TCP option field would be lost along with the original client source IP address and port. However, if this information was included in the HTTP GET Headers then the functionality could in theory be preserved. I know it's a stretch. Peter On Fri, May 4, 2012 at 12:36 PM, Andreas Petersson <andreas@sbin.se> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > On 5/4/12 6:06 PM, Peter Lepeska wrote: > > I wonder if the forwarded information should also include TCP > > header options ( > > http://www.networksorcery.com/enp/protocol/tcp.htm#Option > > <http://www.networksorcery.com/enp/protocol/tcp.htm#Options>s) > > based on the TCP connection carrying the original GET request. > > > > Peter > > Can you provide a use case? > > /andreas > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.4.9 (Darwin) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ > > iQIcBAEBAgAGBQJPpAWbAAoJEEaYRbQUWNlea4wP/jwcy7ZRC2caJwYv/1/9+V/u > SkUUrAl+7H6aVrV0waOSZI2okAZQ9ezBJxJxetiDp1f6wA2h23luJXrW1SOAsANY > VX5RTyWNwbgu51qLILDevpjHk61HvslVch4Qjh0YnOgEhWISz3eHAIzt9jocNAfo > 5x2jf7SuzftVmy84dQlp1u5Rss4V+w8Jr9h+2I8wVxf/LDDSS5wNKXFbwBmHmEDY > dZUnKfpf4Udu3M3JnAjBR6b2WLjSZAFWeK01bKCbZxczfCYZxgeLhMm6r641+M+t > 9TM4YMBUQdY60L/wwKs2E+44xdyU4LtdvdI9Lbfvu/w7jBwj800lT3sUg69GqaaQ > 5qXPKBkJ/1bZKB6u5ryPMTI2n6XMCloiII59b+MiwlCcui5+VJuowiiUZqfL3qyK > OUvJ0S5DlnQUb9h2a87e2wKoO5tZ3udqCXf6CRaraTcvKm8H6y3kCWhXD2M3FLel > pHEJouXpOPB6fzbcCkVO/W4ijnAtWXp0iBz6uQXLairFVRGu5kjN73RfXb53tdz/ > jqsGSjQGxMgMbElvAwk2ZpNQHgXzElvaoj7YvOAkhnikcI6+rcUhjgpTm0hWxmUu > AUyMNOln1wAe4UMxrj2MiYXeULoWlVhZ28alGnho3tcTikyzct2cRIwxkuL+/WfH > eY5wv8T+R/rc0fYuKC64 > =MGh5 > -----END PGP SIGNATURE----- > >
Received on Friday, 4 May 2012 21:11:52 UTC