On Wednesday 27 August 2008 19:24:53 Christoph Biedl wrote: > Joost Yervante Damad wrote... > > > On Wednesday 27 August 2008 11:52:18 Christoph Biedl wrote: > > > Now I noticed that at least for HTTP the extremely useful "Follow TCP > > > stream" function ignores all data in the second TCP stream. This > > > hides potentially interesting data. > > > > I'd expect this as behavior as this are indeed 2 unrelated TCP streams > > that just happen to use the same ports "by accident". > > In that case selecting a packet of the seconds stream before "Follow TCP > stream" would display that one - not always the first. And the filter > expression automatically set would respect that in any way. Currently it > does not.
Ah, now I get it. So it always displays the first, even if you're following the second. That surely is a bug. It should use the selected packet as a location hint. Thanks for reporting it! Joost -- homepage: http://damad.be/joost photo/blog: http://damad.be/joost/blog -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
