Tip / Sign in to post questions, reply, level up, and achieve exciting badges. Know more

Wi-Fi Combo

MuOr_1658816
Level 4
First like received
Level 4

It seems like the dynamic content callbacks only return the URL parameters and not the POST body content. Is there a way to retrieve the POST content?

2 Replies
Anonymous
Not applicable
We are aware of the current limitations of the HTTP server and are working on improving it.

The content of the packet can be found after the end of URL pointer providing in the arguments however the length of valid data is not available.

In the interim while we are fixing this issue feel free to modify the source to pass the required information down to your dynamic content callback.

One option is to pass the packet received in http_server_thread_main() all the way down to the dynamic content callback either as an extra function argument or store it in the wiced_tcp_stream_t object.

The solution we are working on will expand on the capabilities of the wiced_tcp_stream_t object to include stream reading as well as writing and will store received packets internally.
0 Likes
MuOr_1658816
Level 4
First like received
Level 4
We are aware of the current limitations of the HTTP server and are working on improving it.

The content of the packet can be found after the end of URL pointer providing in the arguments however the length of valid data is not available.

In the interim while we are fixing this issue feel free to modify the source to pass the required information down to your dynamic content callback.

One option is to pass the packet received in http_server_thread_main() all the way down to the dynamic content callback either as an extra function argument or store it in the wiced_tcp_stream_t object.

The solution we are working on will expand on the capabilities of the wiced_tcp_stream_t object to include stream reading as well as writing and will store received packets internally.

Sounds good. I hope it will support gziped content also.
0 Likes