On 5/21/2011 12:37 PM, Alan Melia wrote:
> This is the first time I have seen this on a PIC but it is a common error=
 if
> the URI processing is not done correctly.  Taking a wild stab in the dark
> I'd start looking at the hostname processing.  Not saying this is your
> problem but I have seen instances where people assume the URI is always
> going to be an IP address so simply count the number of '.' before trying=
 to
> process the path.  If this is what is happening the you could get a 414
> because it could walk off the end of the string before finding the last '=
..'.
>
> 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 y=
ou
> any more than what you know already.
>
>   =20
I don't think the browser making the request is internal to the PIC. May=20
be but don't think so.
Wireshark the input side and see what the NAT and DNS are doing to the=20
HTTP request.
If one input works and the other doesn't then determining the difference=20
in packets may help.

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