I'm trying to use the zap proxy running on docker image. It works good on my local machine but when trying to use it behind corporate network the zap proxy requests timeout because it can't connect to the internet. I already have configured the http_proxy and https_proxy environmental variables but it seems that zap proxy isn't using them
You can configure a chained proxy (outbound proxy) for ZAP to use. Via Tools : Options > Connection (in the GUI), or the endpoints below in the API.
optionUseProxyChain
optionUseProxyChainAuth
optionProxyChainName
optionProxyChainPassword
optionProxyChainPort
optionProxyChainPrompt
optionProxyChainRealm
optionProxyChainSkipName
optionProxyChainUsername
proxyChainExcludeDomains
Related
I am trying to hit an API using IP port. But the Machine is behind a VPN. Even though my local is connected to the VPN, the HTTP connection is refused. Is there any provision to setup up VPN/Proxy in Karate Framework?
Yes. Please refer to the documentation: https://github.com/intuit/karate#managing-headers-ssl-timeouts-and-http-proxy
I have a squid proxy container on my local Docker for Mac (datadog/squid image). Essentially I use this proxy so that app containers on my local docker and the browser pod (Selenium) on another host use the same network for testing (so that the remote browser can access the app host). But with my current setup, when I run my tests the browser starts up on the remote host and then after a bit fails the test. The message on the browser is ERR_PROXY_CONNECTION_FAILED right before it closes. So I assume that there is an issue with my squid proxy config. I use the default config and on the docker hub site it says
Please note that the stock configuration available with the container is set for local access, you may need to tweak it if your network scenario is different.
I'm not really sure how my network scenario is different. What should I be looking into for more information? Thanks!
I need a way to use Glassfish 3.1.2.2 admin service (REST call to deploy and configre) from a remote machine and from local machine (command line and applications).
It is clear that for remote access it is necessary to enable secure admin. If we enable secure admin it will break all local access from applications. These application can not be changed to using https to access the admin service. Only thing I can change is that we can use a different port.
I see two possible ways for me:
Using a hack. So I can administrate with secure administrate disable. So I can use plan http. For use a possible solution, because this machine used internally in a test environment.
Configure Glassfish that we can use admin service remote via secure access https and from a local environment with http.
We prefer solution 1, because it fit better in our environment and we have lesser effort. At the moment I see no way or exist a solution (not for production)?
I tried something for solution 2, simular to http-listener-1 http-listener-2. So use two ports 4848 for local unsecure access and as example 4949 for remote secure access.But I always fail with configuration. So I start with a step by step configuration. First enable admin interface oon two ports and as second step I want to add the secure access to the new port admin-listener. But I got only one of the ports working.Please can anyone help me with target configuration? Any domain.xml will be welcome.
Thanks florian
You can try to use SSH and run asadmin utilities from remote machine.
Is it possible to deploy a node.js app on Cloud Foundry that listens for HTTPS requests on port 443?
I can find various references to SSL support in the Cloud Foundry forums, but no actual examples of HTTPS apps. The article "Setup SSL on cloudfoundry landscape" seems to indicate that I need to install nginx and use that, but there is not really enough information there to tell me what I need to do.
The SSL connection will terminate at the loadbalancer and then forward the unencrypted HTTP connection to your node app.
Just use https://your-app.cloudfoundry.com instead of http://...
You don't need nginx in particular, but you do need something capable of listening to a port (which Cloud Foundry will assign at the moment, indicated by the environment variable PORT or, for older versions of Cloud Foundry, VCAP_APP_PORT). So nginx will work for this purpose, but if you have made a node.js app, the core module http (optionally paired with express) would be a more natural choice of webserver.
Now if your app requires ssl, you'd think that you'd need to configure your webserver (nginx, express, etc.) for HTTPS, but you do not need to do so because Cloud Foundry handles the SSL and passes the decrypted HTTP to your webserver.
So if you are using node.js core modules, use the http, not https module.
I have an artifactory within a corporate network. I configured a http proxy for each remote repository. It doesn't work. How could I possibly find out why it doesn't work? Are there any log settings which I could tweak?
Using the same proxy within Firefox works just fine.
Artifactory 2 uses logback for logging, you can find its configuration in $ARTIFACTORY_HOME/etc/logback.xml
If you can access the repository through the browser, it's likely the problem is in your Maven configuration. If you've a proxy configuration defined, you'll need to ensure the proxy is set to exclude your internal http proxy server.
If you run Maven with the -X switch, it will give you more details on the connection attempts Maven is making.