obexapp get failure

[Iain Hibbert]

On Mon, 25 Oct 2010, Maksim Yevmenkin wrote:

> i'm convinced that there is a bug in obexapp (or, less likely,
> openobex library). it appears that "connection id" header is intended
> for multiplexing of several data streams. its pretty much analog of
> http "host" header.

for what its worth, obexftp-0.20 exhibits the exact same behaviour as
obexapp.

(there are later versions but I can't be bothered to try and build them at
this time, I have submitted patches to clean up Bluetooth support on *BSD
over a year ago but the git repository shows no related activity)

> i think its clear what "connection id" header must be present on all
> requests from the client, including continue-GET request. what is not
> entirely clear if the server responses should also contain "connection
> id" header. i think they should as well. clearly, wm6 server is not
> sending "connection id" header back in its responses, so perhaps its a
> double whammy.

Hm, are you saying that if the server included the Connection ID in its
GET-response, would that make it to the continue-GET (because of
OBEX_ObjectReParseHeaders() call)?

iain