I am updating libraries to include proxy headers such as host, port, username and password because some users of the library are running behind corporate proxy / firewall. Anyone have a good way of testing this on a Mac? I am not behind any proxy.
I tried setting the web proxy in Network in System Preferences on the Mac but that only seems to affect browser requests. I'm finding that curl requests and anything run in terminal does not go through that proxy.
I have the proxy profile added with a working proxy(checked through curl). I have also setup the proxification rules using the individual applications as well as tried setting the default rule to connect via the proxy profile. But to no avail. When I look up my ip address i see my real IP not the proxy.
It was working fine earlier before i changed the Name Resolution settings to "resolve hostnames through proxy". But now even when i change the Name resolution settings to "Detect DNS settings automatically" my traffic is still going direct through my isp and not the proxy.
The connections list shows all the applications connecting through the proxy but still what is my ip and whoer.net show my real ip address.
Can somebody please guide me through this, i desperately need this to route through a proxy. I am particularly trying to use noxplayer to connect to a proxy.
I have set up a squid proxy on a Ubuntu machine, and I'd like to do some testing by accessing the proxy from another computer (NOT on the same lan). But I seem to be unable to connect to the squid proxy server.
I've tried several different ways to connect: by setting the proxy in my web browser, and by using the unix program "curl" to issue http requests from a command line. But I just can't connect.
I've tried setting the acl in the configuration file squid.conf to allow access from the remote machine. So I don't know what's going on. If I try to access the internet from the same machine that the squid proxy is on, it works correctly.
The lines in squid.conf that I added to allow access from the remote machine are:
acl my_machine src 50.193.61.125/255.255.255.0
http_access allow my_machine
Is there anything else that needs to be done to allow the remote machine to access the squid proxy?
Thanks.
got the same problem. ec2 instance with fedora 19 os and squid 3.2.9. also created a security group incoming rule for port 3128. wont work if i connect from a remote pc. think there is a restriction in the aws-cloud.
I have looked at the documentation for proxy settings (specifcally the proxy mini-howto) in order to use maven with Tor. When I try to connect to Tor with the default port 9050, there is an error in the Tor message center that states Warning: Socks version 71 not recognized. (Tor is not an http proxy). How do I configure maven to work through tor?
(Also note that the suggestions at the Stackoverflow question How do I use maven through a proxy? were not succesful)
Since tor is not an HTTP proxy (like you commonly find in corporate environments) you have to specify the Java networking properties for SOCKS proxies on the command line.
See this answer to the question you linked to.
I am a newbie about SVN server. I've certainly used SVN to check in/out codes before, but never learned how to setup a Subversion server it up from ground up.
What I have:
Server | Windows Server 2012 Standard, Activated:
Installed Collabnet Subversion Edge,
Created a repository,
Created users and also started the server, using start button at GUI on localhost:4434/csvn/.
Client | MacOSX Mountain, with Xcode 4.5 Installed:
I have tried to add repository by using the external IP address and the repository name
like https://1.1.1.1/svn/, but as expected, it does not work and says "Host is unreachable".
I have tried to use the local hostname, no luck either. Although I did notice in their documentation, they mentioned IP address setting, but I cannot find it anywhere.
I would like to make it so that users can access and use the SVN repository remotely and locally.
I have no idea what to do, please help me. Thanks for your time!
Go back to the server for a minute. When you are configuring it, are you only using the local web browser? Have you tried accessing the server using web browser from your Mac? I would see if the Mac can reach the web gui first. Maybe you have network issues you have to resolve, such as DNS, routing or firewall.
In terms of using XCode, or any SVN Client, the URL you must enter is the URL to your repository. That will not be:
https://1.1.1.1/svn/
It will be something like:
https://1.1.1.1/svn/reposname
In the Subversion Edge web GUI if you go to the list of repositories, you will see an example checkout command next to each repository. This command shows you the URL to enter in a SVN client to reach the root of the repository. Example screenshot here:
https://ctf.open.collab.net/sf/projects/svnedge/screenshots/screens/repos/repos.png
I think I have sloved the problem. I knew I have to access the repo using my external IP address somehow, but when I tried something like, for example my IP is 1.1.1.1, when I typeed https://1.1.1.1/svn/reposname, I got a no response message.
I figured that since there are more than 1 computers on my local network, the router has to somehow direct the request to my server only, not some other machine. After some reaserch I found that port forwarding does the trick. Since apache server uses port 80 as default, just get the default gateway ip using ipconfig from CMD, then enable port forwarding for port 80, to the server's local ip address. At least I can access it using my external ip on my local network. I will try to access it remotely and see.