W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2003

Re: HTTP MIME types question

From: Voronkov Konstantin <beowinkle@mailru.com>
Date: Wed, 19 Mar 2003 09:57:22 +0300
Message-ID: <002e01c2ede4$cd721f50$1400a8c0@echotech.ru>
To: "Mark Nottingham" <mnot@mnot.net>
Cc: <ietf-http-wg@w3.org>

Thanks a lot for your notice.
 I did that mistake by inattention.

Best Regards,
Voronkov Konstantin

----- Original Message -----
From: "Mark Nottingham" <mnot@mnot.net>
To: "Voronkov Konstantin" <beowinkle@mailru.com>
Cc: <ietf-http-wg@w3.org>
Sent: Tuesday, March 18, 2003 8:54 PM
Subject: Re: HTTP MIME types question


> In both cases, that should be:
>
> Cache-Control: no-transform
>
> Regards,
>
>
> ----- Original Message -----
> From: "Voronkov Konstantin" <beowinkle@mailru.com>
> To: "Alex Rousskov" <rousskov@measurement-factory.com>
> Cc: <ietf-http-wg@w3.org>
> Sent: Tuesday, March 18, 2003 1:08 AM
> Subject: Re: HTTP MIME types question
>
>
> >
> > Alex, thanks for help.
> >
> > My application sends binary data so I decided
> >  to use for POST data posting
> > "Content-Type: application/octet-stream"
> > For preventing data modifying by proxies I decided to use no-transform
> > directive.
> > For requests
> >  "Cache-request-directive: no-transform"
> > And for responses
> >  "Cache-response-directive: no-transform"
> >
> > Best Regards,
> > Konstantin
> >
> >
> > ----- Original Message -----
> > From: "Alex Rousskov" <rousskov@measurement-factory.com>
> > To: "Voronkov Konstantin" <beowinkle@mailru.com>
> > Cc: <ietf-http-wg@w3.org>
> > Sent: Thursday, March 13, 2003 7:07 PM
> > Subject: Re: HTTP MIME types question
> >
> >
> > > On Thu, 13 Mar 2003, Voronkov Konstantin wrote:
> > >
> > > > I have a question about HTTP MIME types. Our company created
> > > > application which uses HTTP protocol for communications. What is the
> > > > best MIME type to use?
> > >
> > > Depends on the kind of content your application is transmitting as
> > > HTTP payload. Usually, one of the registered MIME types fits well
> > > enough. If not, you can use (and register) your own type. Here is what
> > > Section 3.7 of RFC 2616 has to say:
> > >
> > >    Media-type values are registered with the Internet Assigned Number
> > >    Authority (IANA [19]). The media type registration process is
> > >    outlined in RFC 1590 [17]. Use of non-registered media types is
> > >    discouraged.
> > >
> > > You may want to read Section 14.17 of the same RFC as well.
> > >
> > > > Can any proxy change content (e.g. for security reasons) if I use no
> > > > HTTP MIME type?
> > >
> > > Some proxies might. Proxies are known to guess content type by URL
> > > extensions and other methods.
> > >
> > > > Some of proxy servers can try to cut banners, remove sounds and so
> > > > on. How can I avoid this?
> > >
> > > There may be several ways, depending on your environment.  What are
> > > you sending (HTML, text, opaque bytes)? Who is the client (browser,
> > > custom plugin, applet)? Do you control your clients? In general, using
> > > the no-transform cache-control directive may be a good start (see
> > > section 14.9.5 No-Transform Directive).
> > >
> > > HTH,
> > >
> > > Alex.
> > >
> > > --
> > >                             | HTTP performance - Web Polygraph
> benchmark
> > > www.measurement-factory.com | HTTP compliance+ - Co-Advisor test suite
> > >                             | all of the above - PolyBox appliance
> > >
> > >
> >
>
>
Received on Wednesday, 19 March 2003 01:59:14 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 27 April 2012 06:49:22 GMT