inconsistent documentation on expected return for dynamic license model generation HTTP response

dbb · ‎03-17-2009

The longstanding dynamic licence flow PDF at http://us.blackberry.com/developers/appworld/Dynamic_License_Flow.pdf says:

The vendor portal expects the following response:
HTTP/1.1 200 OK
Content-Type: application/www-url-encoded
Content-Length: 20
key=ABCDEFGHIJK

The page at http://supportforums.blackberry.com/t5/BlackBerry-App-World-Development/The-BlackBerry-App-World-lic... says:

It is expected that the vendor's server will respond with only the key in the following format:

HTTP/1.1 200 OK
Content-Type: text/html
Content-Length: 8

key=abcd

1. Which is correct? What is the proper Content-Type to return: "application/www-url-encoded" or "text/html"? Or the content type that implies URL encoding and is actually standard: "application/x-www-form-urlencoded"?

2. Can somebody at BlackBerry please fix the incorrect documentation?

Thanks.

adwiv · ‎08-01-2008

I believe the server does not care about your content type.

What is shown is actually the header as well as the body of the response.

Just output the key=xxxxx in the output of your script and you should be good to go.

Welcome!

BlackBerry® World™ Development

inconsistent documentation on expected return for dynamic license model generation HTTP response

Re: inconsistent documentation on expected return for dynamic license model generation HTTP response