Yeah.  Nothing special needed to be done to the browser.

On Wednesday, January 8, 2014 1:20:03 PM UTC-5, Chuck van der Linden wrote:
>
> On Wednesday, January 8, 2014 9:38:15 AM UTC-8, Dan wrote:
>>
>> Actually, I was confusing some work I've done with wireshark and fiddler. 
>>  Wireshark has a command line interface that I've used.  This was actually 
>> done in a powershell script and not ruby, but it's the same idea. 
>>  Wireshark might be a little too low level though? 
>>
>> You can pass the interface you want to monitor and filters and such.
>>
>> c:\Program Files\Wireshark\Wireshark"  -i Wi-Fi -k -w  $($path)
>>
>> http://www.wireshark.org/docs/wsug_html_chunked/ChCustCommandLine.html
>>
>> Looks like in ubuntu you can get it from the software center and probably 
>> do something very similar via ruby.
>>
>
> When you use wireshark did you need to do anything special when starting 
> the browser?  (like telling it to use a proxy) or does it work more like a 
> network monitor tool that just watches the traffic? 
>
>  
>
>>
>> On Wednesday, January 8, 2014 12:09:26 PM UTC-5, Chuck van der Linden 
>> wrote:
>>>
>>>
>>>
>>> On Tuesday, January 7, 2014 12:06:55 PM UTC-8, Dan wrote:
>>>>
>>>> I've "cheated" in the sense that I've used Fiddler by programmatically 
>>>> starting and stopping it when running tests.  There looks to be a Linux 
>>>> build of it now.  In my case it was ADFS so I feel your pain.
>>>>
>>>> http://fiddler.wikidot.com/mono<http://www.google.com/url?q=http%3A%2F%2Ffiddler.wikidot.com%2Fmono&sa=D&sntz=1&usg=AFQjCNHGL32pXhWZezicvDlNfw8nXkFKag>
>>>>
>>>
>>> If it gets me a usable HTTP log, I'm not sure I would call it cheating. 
>>>  I wonder if there is a standard package to install fiddler on the Saucy 
>>> version of ubuntu, I'd need that to be able to install it on the container. 
>>>  google is not finding me one, so I may be SOL in terms of this approach
>>>
>>> How did you tell the firefox browser instance to use the system proxy 
>>> when you did Watir::Browser.new?  The stuff at the site you referenced 
>>> tells me how to do it manually, but obviously that's not going to work.
>>>
>>> If you have code you could share, that would be wonderful and save me a 
>>> lot of trial and error
>>>
>>>
>>>>
>>>> On Tuesday, January 7, 2014 2:31:45 PM UTC-5, Chuck van der Linden 
>>>> wrote:
>>>>>
>>>>> This stackoverflow is very similar, and has no answer so far  
>>>>> http://stackoverflow.com/questions/19178901/integrate-watir-webdriver-and-browsermob-proxy-and-webdriver-user-agent
>>>>>
>>>>> I've got some web pages being very flakey and inconsistent (an SSO 
>>>>> solution based on shibbolith) and we really need to be able to generate a 
>>>>> http traffic log of what happens while the tests are running.
>>>>>
>>>>> Tests run in a unix container
>>>>>
>>>>> Looking around it seems like something such as BrowserMob/proxy might 
>>>>> work well, and there is even a  browsermob-proxy gem written by this 
>>>>> 'jarib' guy who I think may know something about watir-webdriver also 
>>>>>  (wink wink) 
>>>>>
>>>>> It seems like it ought to be possible to use watir-webdriver and 
>>>>> browsermob-proxy together to do what is needed to be able to create a 
>>>>> proxy 
>>>>> logfile of a session of watir tests, but I'm a little at a loss of where 
>>>>> to 
>>>>> start.    The browsermob readme gives an example for webdriver, but not 
>>>>> for 
>>>>> watir-webdriver.
>>>>>
>>>>> can anyone tell me how I'd go about using browsermob-proxy with 
>>>>> watir-webdriver? 
>>>>>
>>>>> --Chuck vdL  (posting from the work email since this is work related) 
>>>>>
>>>>

-- 
-- 
Before posting, please read http://watir.com/support. In short: search before 
you ask, be nice.

[email protected]
http://groups.google.com/group/watir-general
[email protected]

--- 
You received this message because you are subscribed to the Google Groups 
"Watir General" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to