How to use proxy in webkit webbrowser - webkit

I have application i use to connect to internet using proxy and i use for that webkit webbrowser . The problem is that webkit webbrowser do not accept proxy.
So how i can make webkit webbrowser to use proxy like the ordinary webbrowser that came with vs 2012 ?
Any help will be appreciated.

Related

Is Selenium a security vulnerability?

I'm learning Selenium but I am concerned that the Webdriver (Chromedriver.exe, Geckodriver.exe) seems to open a port for communication functioning as a proxy between the selenium code and the browser. I don't want to expose myself to any vulnerabilities and would prefer some form of direct browser communication. I've viewed several solutions, but selenium just seems to be the reigning champion.
It appears that some form of what I am looking for was present with PhantomJS, but that seems to be no longer supported. This leaves me two options:
-Find a browser that selenium can communicate directly with without the aid of Webdriver.
-Find a way to completely restrict that port that it seems to open up so it does not allow connections from anybody on the network and no one can connect to my local machine.
Any suggestions folks?

Does selenium grid runs only Selenium command or also code chunk from different library

I have done my automation in Robotframework and I am using many libraries like Selenium2Library, Sikuli Library, HTTP Library, OS library and few more.
When I am running test on Selenium Grid, it invokes the browser on node and runs those steps which are from Selenium.
However, it does not run commands from Sikuli Library. Is selenium grid capable of running keywords from different libraries?
No, the selenium grid only works with selenium. The selenium grid is a server much like a web server. It listens for specific commands, and performs those commands. It will only respond to commands from selenium clients.
When using Sikuly in Robot Framework it is necessary to first setup the external sikuly server and then connect to it from Robot Framework. Typically this is a localhost connection, but connecting to an external host is also possible.
When using Selenium Grid, a connection is made to an anonymous node and thus the host to which the Sikuly server is runnning as well. Did a quick check in google and found that getting the hostname/IP of the running node from the hub is possible. Using the code example here I think it should be possible to create a direct connection to the Sikuly server.

Mobile analytic using selenium and appium

I'm able to do analytics testing using browsermob and selenium in my previous project, but 'm not able to do same with mobile web using appium and selenium.
Though m able to start the proxy server but not able to bind it with my mobile web.
Thanks
I'm closing this question as i got the answer. FYI its same as for desktop only we have to set ours mobile proxy to same before starting the test.

Remote Desktop Web client

I have few Cloud based Windows box connected with internet and I wanted to access the same from my office network.
The problem here is, my office doesn't allow direct RDP to any internet connected pc as we normally access all sites using proxy.
Is there anyway I can connect through web based client? I tried TSWEB/RDWEB but again it seems using local port number.
Any suggestion?
Thanks
bala
I found another client "ThinRDP" which works as expected. Thank you all for your help
I suggest that you try Igiko Management Tools and forget about such problems. It has embedded Web RDP + Gateway + Tunnel. Works from anywhere.

Selenium1 - Commands are failing in Mac - Safari5 on HTTPS page

I m using selenium1 to automate my web application. Recently i started running test cases in Mac machine and found few issues. Selenium methods are not working correctly in Mac machine Safari browser(Ver. 5) on https pages. Any workaround for this?
Thanks
This page implies there is not good support for your scenario in Safari:
Sauce OnDemand is configured to take full advantage of what Selenium
can do, though some limitations do remain, such as poor Safari support
and trouble navigating between HTTP and HTTPS domains.
Are you using *safari or *safariproxy? Is the SSL certificate self-signed or valid? You could try switching those.