>> This real problem is not that we can't have the entire url, but in
>> these case, even the HTTP Version and the CRLF is truncated .... so it
>> causes lot of problem for my parser ....
> That's probably because the request or response doesn't fit in one
> segment.
>>I just want to know if it is a bug,
> It's a deficiency, not a "bug", strictly speaking - versions of Ethereal
> prior to 0.9.16 didn't have code to reassemble requests or responses
> that crossed TCP segment boundaries, but they didn't claim to reassemble
> them.
>> and if there is a way to solve it ....
> Upgrade to Ethereal 0.9.16, if you're not already running it.
> Then start up Ethereal, select "Preferences" from the "Edit" menu, open
> up the "Protocols" list in the Preferences dialog, select "HTTP", turn
> on the "Desegment all HTTP headers spanning multiple TCP segments"
> option", click "Save", and click "OK".
> That will tell Ethereal *AND* Tethereal to reassemble HTTP requests and
> responses (method/status line, and headers) if they don't fit in one TCP
> segment.
ok It work thx a lot, the packet are desegmented, but i have still an unsolved problem.
If the url is too long (nearly 240 bytes), the url under tethereal (not ethereal) is truncated.
Maybe is there a way to upgrade the size of the url's flag ?
thx