Another MIME-related problem

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Another MIME-related problem

Igor Stasenko
Image is pharo-dev #10259

Try following:

(Installer monticello http: 'http://scribo.aidaweb.si/repository')
install: 'Scribo-np.172'.

it says that 'unknown' mime type is invalid.
I don't sure if it problem on a server side - Aida, or its because of
changes to MIME..

Are 'unknown' mime type string is valid mime type?

--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Another MIME-related problem

Michael Rueger-6
Igor Stasenko wrote:

> Image is pharo-dev #10259
>
> Try following:
>
> (Installer monticello http: 'http://scribo.aidaweb.si/repository')
> install: 'Scribo-np.172'.
>
> it says that 'unknown' mime type is invalid.
> I don't sure if it problem on a server side - Aida, or its because of
> changes to MIME..
>
> Are 'unknown' mime type string is valid mime type?

AFAIK it is not a legal mime type, so it is a server side problem. It
should return a default mime type like application/octet-stream.

Having said that, I've changed the code so it converts 'unkown' into
'application/octet-stream'. Available in the inbox as

Network-MIME-michael_rueger.8


Michael

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
Reply | Threaded
Open this post in threaded view
|

Re: Another MIME-related problem

Igor Stasenko
2009/3/25 Michael Rueger <[hidden email]>:

> Igor Stasenko wrote:
>> Image is pharo-dev #10259
>>
>> Try following:
>>
>> (Installer monticello http: 'http://scribo.aidaweb.si/repository')
>> install: 'Scribo-np.172'.
>>
>> it says that 'unknown' mime type is invalid.
>> I don't sure if it problem on a server side - Aida, or its because of
>> changes to MIME..
>>
>> Are 'unknown' mime type string is valid mime type?
>
> AFAIK it is not a legal mime type, so it is a server side problem. It
> should return a default mime type like application/octet-stream.
>
> Having said that, I've changed the code so it converts 'unkown' into
> 'application/octet-stream'. Available in the inbox as
>

NONO! If MIME standard says its illegal - let it be illegal.
I think this is fair to force devs to follow standards.

What i can guess, that maybe there is no need to throw an error: i.e.
if content-type is malformed, it can simply
do:

^self
                main: mimeString
                sub: ''
                parameters: ''

in #fromMIMEString: method.

because i think nothing bad will happen later - if content type is
unknown , then all applications who care about it will anyways be
forced to use them as a simple octet stream.
Monticello doesn't care about proper MIME type, and it can continue
running without any problems (this is what i actually did - returned
(self main: mimeString sub: '' parameters: '') using debugger to
install the needed package despite the error with MIME).


> Network-MIME-michael_rueger.8
>
>
> Michael
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

--
Best regards,
Igor Stasenko AKA sig.

_______________________________________________
Pharo-project mailing list
[hidden email]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project