Packet size too big? - SimpleClient

[GregEigsti]

Just committed/pushed this change to the user contrib branch. Tested with both TCP and WiServer (SimpleServer) app. Weird thing is that SimpleServer would not return data to latest version of Safari but did respond to curl.

I'm not entirely sure that WiServer is sane in the user contrib branch and probably should look into it

My MacBook Pro is dying on me so I wanted to get these changes pushed before it goes South again...
Greg

[aerodyno]

Has anyone tested this fix? It's a great one, if it actually works.

[aerodyno]

So the way to test this, as Jared points out, is use

ping -l 1400 [sensor_ip]

and I'm happy to report that IT WORKS. Nice.

-s

[GregEigsti]

Thanks for reporting back! WiServer died in the user contrib branch shortly after I added this fix. Sooooo, it does not seem like this fix should have broken WiServer but I am suspicious (and probably way off base).

If I only had more time I could get to investigating and fixing

Thanks!
Greg

[GregEigsti]

I just reverted this fix back out of the user contrib branch as it was the culprit in the murder of SimpleServer and WebServer. Something not understood that should probably be looked into and fixed. Weird thing is that it works for some (if my re-reading of this thread is correct).

Anyway, it is out of the user contrib branch - anybody using the user contrib branch and running into the original problem can try their hand at a fix and report it back to the group.

Greg

[aerodyno]

It worked for me in that it successfully allowed HTTP POSTS, I never actually needed the webserver part.

[GregEigsti]

Your HTTP POSTs worked before and/or after removing the "packet too large" fix? I got lazy and threw this fix in with minimal (if any) testing

Thanks Aerodyno!
Greg