NON-DELIVERY of: Re: Parameters in Content-Type: headers; what the???

LMasint@MAIL.ZD.ziff.com (LMasint)

Mail folder: WWW Talk Apr 94-present
Next message: ORonqui: "NON-DELIVERY of: PLEASE ACCEPT MY APOLOGY. SORRY!"
Previous message: Simon E Spero: "Re: statelessness "
Maybe in reply to: MVanHey: "NON-DELIVERY of: Re: Parameters in Content-Type: headers; what the???"

Errors-To: listmaster@www0.cern.ch
Date: Sun, 29 May 1994 04:57:39 +0200
Errors-To: listmaster@www0.cern.ch
Message-id: <01HCSQ5N1GHE002UR3@zcias1.ziff.com>
Errors-To: listmaster@www0.cern.ch
Reply-To: LMasint@MAIL.ZD.ziff.com
Originator: www-talk@info.cern.ch
Sender: www-talk@www0.cern.ch
Precedence: bulk
From: LMasint@MAIL.ZD.ziff.com (LMasint)
To: Multiple recipients of list <www-talk@www0.cern.ch>
Subject: NON-DELIVERY of: Re: Parameters in Content-Type: headers; what the???
X-Listprocessor-Version: 6.0c -- ListProcessor by Anastasios Kotsikonas

Intended recpient(s): Steve Browne @ ZD Europe
Failure reason: Router: Unable to open mailbox file NAPOLEON mail.box: You are not authorized to use the server
O-CMS-ErrorsTo: listmas @ INTERNET (listmaster) {listmaster@www0.cern.ch}
Given how new the web is, and how wet the ink on the specification is,
don't be surprised that the browsers don't conform to the
specification. Usually, network protocol standards take years to shake
out. That the web has grown as quickly as it has is phenomenal;
however, I don't think we can avoid a year or two of shakeout (if not
more) as the specs get re-written, browsers and libraries get brought
into conformance, etc.