MM7 Request

MM7 Request SearchSearch
Author Message
Rene Glembotzky
Unregistered guest
Posted on Thursday, February 05, 2004 - 03:09 pm:   

Hi,

we are evaluating NowSMS and have problems with the Content-Type parameter. Our MMSC provider has the problem that the type parameter should be quotated, e.g.

Content-Type: multipart/related; boundary="---mime-boundary-679C34D5.9ED0CD16---"; type="text/xml"

In the original NowSMS request the quotation marks are missing (type=text/xml). Is there any possibility to customize this parameter???


tia,

rene glembotzky
Bryce Norwood - NowSMS Support
Board Administrator
Username: Bryce

Post Number: 1857
Registered: 10-2002
Posted on Thursday, February 12, 2004 - 05:32 am:   

Hi Rene,

It is amazing how picky some applications can get for no good reason.

Putting quotes around the value of the type= parameter should not cause any problems. We'll go ahead and make that change. Send an e-mail to nowsms@now.co.uk to request an update that includes this change.

If we run into other problems, then we will have to make this configurable.

However, I think the change is a good idea, and I'll explain why. The MM7 examples in the 3GPP MMS specification do not include quotes around the type parameter value. So they look just like the headers that we currently generate.

However, I thought it was worth referring to the HTTP specification. The HTTP specification states that Content-type parameter values are of the type token. And it further states that if special characters are included in a parameter value, then a quoted string must be used. The "/" character is one of these special characters, and therefore my interpretation is that according to the HTTP spec, "text/xml" should be a quoted string.

So there you have it ... alert the 3GPP ... they may be up to release 6.4.0 of this particular specification, but it is clearly in error.

That said, I think it is rather ridiculous that an implementation of MM7 could not handle an example from the specifications ...

-bn