suggested this on January 06, 2012 12:00 PM
My current implementation with browsermob proxy works fine with my local machine but getting the har file does not seem to be working remotely. Is there additional configurations I need?
There currently isn't a way to handle proxying and getting an har file for browsers in our cloud. This certainly sounds like a great feature request. I'm moving this to the right forum.
browsermob-proxy support is something I've been looking for also. They have a REST API
Would be fantastic to verify that various calls are occurring and succeeding in each of the environments we run our tests inside of sauce labs.
will you be adding support for all the other browsermob-proxy features such as http request/response manipulation and bandwidth latency? Our tests rely on that lib and it's the only reason we haven't considered saucelabs yet. Thanks!
Does anyone know if this available? Is it possible to use my own browsermob-proxy installation and then connect to sauce labs?
eagerly waiting on this!
Thanks for your input. We're prioritizing a few exciting new services (including mobile and Mac integration), and may tackle this afterward since it has strong community interest. You can stay tuned via our blog at sauce.io .
Is Mac integration including SafariDriver support for Selenium 2?
Hi daluu, thanks for asking. We have Mac VMs with Safari planned for release in late August / early September. Our blog ( sauce.io ) will have info on that as well, as soon as it's available.
Is there an update on using browsermob to capture network traffic? I recently switched a client's code from Selenium RC to WebDriver. Because WebDriver doesn't capture network traffic, we had to disable the tests that make assertions about response headers.
Plus one vote. This would be a very useful feature for us.
We've found this to be a priority for a couple of clients in the last year. Specifically, browsermob-proxy fills a couple of big gaps in Selenium: the ability to inspect and manipulate requests at a low level. It's critical for testing sites that requires custom headers or http authentication, for example.
I think there is definitely enough traction for this topic. Is this in saucelabs roadmap in the near future?
This is a very important feature for us.
+1 for us as well.
I've been doing this by using SauceConnect with the -p flag. In my case it's -p localhost:9090, where 9090 is the port on which the proxy is running -- NOT the rest service.
It'd actually be really nice if you could have SauceConnect request a new proxy via the REST API for each browser session. As it is now, if you try to run multiple sessions vs one proxy, it becomes very hard to disentangle your HAR files. I'm forced to run my tests serially for now. :/
+1, my team would really benefit from this as well
Currently this works with Sauce Connect 3 and browsermob proxy, but upon upgrading to SauceConnect4 i see some issues. WIth SauceConnect4 the --proxy option is for sauce connect itself to reach out to saucelabs, the -T option used to specify the proxy configured for the tunnel, but none of these seem to be of any use when trying to proxy browser traffic to browsermob, does 4.0 not include these features?
Support Ticket System by Zendesk