Olin Lathrop wrote:
> Alan Melia wrote:
>  =20
>> I've seen comments about using Wireshark but this is internal to the
>> PIC so all you are going to see is the 414 response which is not
>> going to tell you any more than what you know already.
>>    =20
>
> Wireshark could show you the URI the PIC is actually sending out with the
> request that elicts the 414 response.  That could be illuminating in trac=
ing
> down the bug.
>  =20
Indeed it would also show you what is in the request OTHER than the URI=20
(since the same URI sometimes causes the request). In particular it will=20
show you what changes between a successful request and a failed request.

What it WON'T really help you with is finding out where in the code the=20
error is generated so the buffer in question can be made bigger.

My gut feeling is that this is a bad error message and it really means=20
"request too large for buffer" (there is more to a HTTP request than the=20
URL). I suspect the buffers were made very tight to fit in an 18F and=20
were never expanded when the stack was ported to processors that=20
actually have the memory to do it properly.
>
> ********************************************************************
> Embed Inc, Littleton Massachusetts, http://www.embedinc.com/products
> (978) 742-9014.  Gold level PIC consultants since 2000.
>  =20

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.