Jeffrey Mogul <mogul@pa.dec.com> writes: >14.QQQ Non-Compliance >... > Non-Compliance = "Non-Compliance" ":" 1#non-compliance-option > > proxy-host = host [ ":" port ] > > non-compliance-option = compliance-option "@" proxy-host This implies that non-compliance-option allows parameters, e.g.: Non-Compliance: MyNameSpace=MyThing;MyParam@Somebody.Else.Proxy Is this an accident of syntax? If not, what is the interpretation of such a header? Two possibilities come to mind immediately: 1) Somebody.Else.Proxy doesn't support the MyNameSpace=MyThing item. 2) Somebody.Else.Proxy supports the MyNameSpace=MyThing item, but doesn't support it with the MyParam parameter. Ross Patterson Sterling Software, Inc. VM Software DivisionReceived on Wednesday, 30 July 1997 09:40:57 UTC
This archive was generated by hypermail 2.4.0 : Thursday, 2 February 2023 18:43:03 UTC