topbanner_forum
  *

avatar image

Welcome, Guest. Please login or register.
Did you miss your activation email?

Login with username, password and session length
  • Monday December 16, 2024, 2:13 am
  • Proudly celebrating 15+ years online.
  • Donate now to become a lifetime supporting member of the site and get a non-expiring license key for all of our programs.
  • donate

Author Topic: URLSnooper Feature Request  (Read 7664 times)

andradrr

  • Participant
  • Joined in 2006
  • *
  • Posts: 3
    • View Profile
    • Donate to Member
URLSnooper Feature Request
« on: November 12, 2007, 07:45 AM »
Hi!

Please, is there any way to put back the capture buffering and parsing feature? It is extremely useful (at least for me...) to be able to buffer (all) the captured packages and then parse one by one in order to understand the handshake between the browser and the server.

I don't know if other people use this feature, but when you face some kind javascript URL stealting, the only way to make things work is parsing packet by packet and see what is happening behind the scenes.

I know I can use some other tools to parse buffered packets, but URLSnooper is extremely easy to use, have a clean interface, and go right to the point to get the job done! In other words, it is the perfect tool!

Thanks a lot!

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 40,914
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: URLSnooper Feature Request
« Reply #1 on: November 12, 2007, 09:46 AM »
Sure i can put it back, i'll make it an option maybe from advanced mode.  I'm not sure why I removed it completely in the first place -- probably just to simplify it.

mouser

  • First Author
  • Administrator
  • Joined in 2005
  • *****
  • Posts: 40,914
    • View Profile
    • Mouser's Software Zone on DonationCoder.com
    • Read more about this member.
    • Donate to Member
Re: URLSnooper Feature Request
« Reply #2 on: June 04, 2008, 03:01 PM »
This is back in the new version as of v2.22.01.