|
Here are some of the enhancements that are on the radar scope. Let me know of others
you think would be useful and how important some of these are to you.
- Proxy servers
Enable WebDebug to be able to use a proxy server to make its requests instead
of trying to connect to servers directly
- Password protection
Password protect access to the WebDebug menu
- Filtering
Be able to filter the contents of the message list by IP address, content-type, etc.
- Replay
Replay the requests in a message list back to their respective servers
- Multiple message lists
The ability to manage multiple message lists simultaneously
- Separate administration port
Instead of the "in-band signaling" method that WebDebug uses now
- Download time estimates
Estimate the amount of time it would take to execute all the request/response pairs
in the message list based on modem speed, latency, etc.
- SSL support
This would enable WebDebug to function with HTTPS as well as HTTP. Will require
quite a bit of hacking since you can't typically "snoop" SSL connections
- Header and field editing
This feature would expose all hidden form fields and certain HTTP headers (e.g. cookies) as normal fields. The developer would then be able to edit these fields on the fly. Useful to testing app behavior and for security work
|
|
|