I'm implementing Transfer-Encoding: chunked, and I'm trying to figure out what to do if I get a chunk-ext I don't understand (which is to say, any chunk-ext, since RFC-2068 doesn't define any). Currently I ignore it and log a warning, on the theory that any future extension should be backwards compatible--but 2068 is silent on whether I can expect compatibility, and I'm not sure what kind of compatible extensions might make sense anyway. Any advice? -- /=============================================================\ |John Stracke | My opinions are my own | S/MIME & HTML OK | |francis@ecal.com|============================================| |Chief Scientist | NT's lack of reliability is only surpassed | |eCal Corp. | by its lack of scalability. -- John Kirch | \=============================================================/Received on Wednesday, 28 April 1999 14:56:31 EDT
This archive was generated by hypermail pre-2.1.9 : Wednesday, 24 September 2003 06:33:30 EDT