Re: ISSUE PROXY-AUTHORIZATION: Proposal wording

Phillip M. Hallam-Baker (hallam@ai.mit.edu)
Tue, 8 Jul 1997 18:14:06 -0400 

This is a multi-part message in MIME format.

------=_NextPart_000_01BC8BCA.B9962210
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


>>I guess you wouldn't want a creative proxy which would re-write
>>BASIC authentication into digest authentication either?
>
>I don't want proxies to be `creative'.  I think that HTTP/1.x should
>not allow creative proxies, and am against weakening MUSTs to allow
>such creativity.

???

A "Creative proxy" is just a gateway. In the HTTP spec proxy is simply
a 
name for a gateway that has the particular property that the source
and
 
destination protocols are the same and the request processing does not
"alter" the request.

The spec can define what is and what is not a proxy but it cannot tell
you
what a gateway can or cannot do, nor can it tell you not to point your
browser
"proxy" resource to a server that is operating as a gateway rather than
a proxy.


Phill




------=_NextPart_000_01BC8BCA.B9962210
Content-Type: application/x-pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIIBCwYJKoZIhvcNAQcCoIH9MIH6AgEBMQswCQYFKw4DAhoFADALBgkqhkiG9w0BBwExgdowgdcC
AQEwdjBiMREwDwYDVQQHEwhJbnRlcm5ldDEXMBUGA1UEChMOVmVyaVNpZ24sIEluYy4xNDAyBgNV
BAsTK1ZlcmlTaWduIENsYXNzIDEgQ0EgLSBJbmRpdmlkdWFsIFN1YnNjcmliZXICEGFDFWiEgdTV
ot4rXibJq8UwCQYFKw4DAhoFADANBgkqhkiG9w0BAQEFAARAR9kdVU8IwEtw/iIGR9RS4BTvew7E
FtTNiowiLVMZaWKlaxTf2vxQNhboeRvx8f/gtr9TaIUVRPrMbNcf50OGTg==

------=_NextPart_000_01BC8BCA.B9962210--