-
Notifications
You must be signed in to change notification settings - Fork 2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
examples/gcoap: take full URI as input #20554
examples/gcoap: take full URI as input #20554
Conversation
281e7ca
to
0d4caf9
Compare
Not the authors fault here but RIOT really should change the way it interacts with URIs. That's awful... Change looks good to me, didn't test it. |
209aa7b
to
ac9032e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM! 🚀
See the minor change request.
Did not test it.
e5b13ba
to
7e97ee8
Compare
I dropped the static IP configuration in the Makefiles I used for testing and adjusted the README. |
Thank you |
Note to self: #18107 needs rebase and major rework. |
adapts the release spec to the changes from RIOT-OS/RIOT#20554
adapts the release spec to the changes from RIOT-OS/RIOT#20554
Contribution description
The gcoap example should better accept an URI as input instead of a host and path.
This avoids some module dependent port selection and prepares the example to deal with different kinds of coap proxies.
The client should be able to specify any scheme independent of modules as dealing with
coaps
or maybe evenhttp
orquic
is the job of the proxy.Testing procedure
As described in #20454.
To get the
/.well-known/core
payload from the libcoap server you still nedd to increaseCONFIG_GCOAP_PDU_BUF_SIZE
.Client:
examples/gcoap
Proxy:
examples/gcoap
Server:
coap-server-openssl -A fd01::1
Issues/PRs references
#20454