I was hoping google chrome socket connections from a chrome extension would go through the proxy settings of the browser but it does not seem to be the case.
Any idea of how could I automagically connect to a server and let chrome bothering with the proxy ?
Currently you can't, but we expect that this will be possible using a network proxy API when the bug http://crbug.com/172285 gets implemented.
If you want, star the issue to follow the development.
Related
I have a web page communicating with my .net application installed on my computer via websocket.
During development I had my page on http://localhost:8009 and everything worked fine with 'ws://localhost:23120/install' in Chrome, FF, IE11.
Now after I deployed my page to public internet server with HTTPS protocol I have an error in IE11: SecurityError. That's it. No additional information.
An Error executing
const webSocket = new WebSocket('ws://localhost:23120/install');
Can that be becourse I open HTTPS page and try to connect to not secure websocket?
Or anything else?
In short. Yes. It is because it is now secure. You should be using
wss://yourdomain.com/install
Remember to setup on the server to allow secure websockets.
I can't seem to get any activity showing on anything relating to HTTP/proxy requests in Ubuntu.
I downloaded Charles Proxy first, opened it, but shows nothing.
Then I tried Interceptor (Chrome extension), also nothing.
Having a look at my Ubuntu settings, it's entirely possible I'm supposed to configure something in here, in support of these options, but it's not documented at all.
How I can go about listening to network requests, intercepting them and serving other/mock json when they happen?
You have to configure Chrome (or whatever the browser you use) to use the Charles Proxy's proxy (as far as I remember: localhost:8888). As this proxy is only running when you have CharlesProxy opened, you probably won't want to define it system wide.
The best option is to use a proxy switch browser extension, such as Switchy Omega (chrome extension) to be able to rapidly toggle on/off the proxy used by the browser.
I want to add VPN client support to an existing chrome extension. I noticed that chrome has an API named 'networkingPrivate' for many network configurations. I kick started with a java script that calls some of the methods provided by networkingPrivate API. But, I'm facing chrome.networkingPrivate 'undefined' error. Any reference on how to use the API in a chrome extension would be of great help!
Chrome OS only, kiosk apps only (not extensions), dev channel only, and it is being renamed.
https://developer.chrome.com/apps/networking_onc
You probably want chrome.vpnProvider instead anyway, but that's still Chrome OS only.
I have a server, created in c++ that accepts TCP connections. We have a few clients that can connect on it (iOS, Android, web). I'm trying to add support for TLS now, but I can't seem to get it right. The TLS connection works when using Firefox, but not when using Chrome.
The code to start the connection is pretty simple:
var socket = new WebSocket(host);
The server side is a bit more complex, it can be found here
I inspected what happens with Wireshark. The results for Firefox can be seen here and the results for Chrome can be found here.
What is going wrong here? Does Chrome require something special before the TLS connection can be established?
I have solved my problem. It turns out that there was nothing wrong with my code, but that Google Chrome has a strict poly regarding certificates. I was testing with an untrusted self-signed certificate. When I tested with the company trusted certificate everything worked.
I want to write an Extension for the google chrome browser which reads some links from a website and copy these links into a file. I want to send this file via ssh to another computer in my local network.
How can I setup and use a ssh connection in my chrome extension?
Assuming you mean scp, not ssh, here are your options:
Set up a WebSocket proxy. Write JavaScript to send the XHR-fetched ArrayBuffer. WebSockets can go over SSL, so you'll probably be satisfied with that rather than implementing SSH in JavaScript (and then scp over that).
Same idea but an HTTP proxy. This would be pretty painful. See Web-based SSH for overview.
Write a Chrome App, thereby getting access to chrome.sockets. Implement SSH in JavaScript. See paramikojs to get started.
Chrome App, Native Client. This can actually work; see Secure Shell. Add scp functionality.
The Chrome-App-based solutions raise a separate question of how to get the web content. You might be able to use Chrome Apps webview. Or you can message the content between the app and a Chrome Extension.
There are probably other approaches as well. But you get the idea: you have a lot of coding ahead of you.