Options not optional?

[nzfarmer1]

I spent sometime last week on getting a client request working from this library.

It spat the dummy on the return message. On investigation the code used to parse the Options made the assumption that there had to be 1 or more options, but in the spec options can be 0 or more.

coap_options.c: 178 if (srcArr[0] == OPTION_PAYLOAD_MARKER)

(This is a later version to the code I was looking at, but my reading of the spec implies that a payload can follow the tokens - something this doesn't allow for, and is always invoked as part of the message processing?)

I could be wrong here though, it was a quick fix to render the response of a coapthon server that may well be violating the spec.

[thebigtimes]

Hi nzfarmer1,

Also currently working through a client request example using the library. I am having issues getting a valid response after my localhost coapthon server receives the initial request message.

Do you mind showing your client code? I will give it a try and see if I am seeing the same thing when using no options.

Thanks.

[nzfarmer1]

Sure thing. I made a few changes to both lobaro and coapthon and have now got observer working with lobar acting as a server. Send me your email address.

[niondir]

Thanks for mentioning the issue. We are open for all pull request addressing the issue.