How would that work? Maybe something like ?forward=http://someurl on your RequestBin path?ORWould it be easier to be able to forward individual requests from the inspector UI?Also, how can you incorporate some sort of security so you can't take advantage of RequestBin as an open proxy?
-jeff
I think adding a option when creating the bin is enough.
For the security issue, I haven't think it through... you are the expert...Maybe the redirected reqs can be applied some freq/time limits?
--Bo
On Sunday, April 8, 2012 8:52:38 PM UTC-4, Jeff Lindsay wrote:How would that work? Maybe something like ?forward=http://someurl on your RequestBin path?ORWould it be easier to be able to forward individual requests from the inspector UI?Also, how can you incorporate some sort of security so you can't take advantage of RequestBin as an open proxy?-jeffOn Sun, Apr 8, 2012 at 8:48 PM, zhuzhuor wrote:
Hi,
Thanks for the excellent work!
I am thinking if it is possible to add a functionality for requestbin
such that it will also resend the received requests to target servers,
which means requestbin will record request data and serve as a proxy
at the same time.
I think this would be more helpful for debugging in some scenarios.
--Bo
I think adding a option when creating the bin is enough.You mean providing the URL to forward to when you create the bin?
For the security issue, I haven't think it through... you are the expert...Maybe the redirected reqs can be applied some freq/time limits?It would probably be a ridiculously low rate ... like 3 req/sec. And it wouldn't be for a while because it would take a bit more thinking and somewhat non-trivial engineering.
Well thanks for the suggestion and ideas around it.