I am just working on proxy server load test. I running the JMeter with properties jmeter -H <my proxy domain> -P <my proxy port>. The proxy will work if we override the User-Agent with our custom User-Agent, and i am using HTTP Header Manager to do the job.
The problem is, it's worked if i am hit into HTTP protocol, but the JMeter won't override the user-agent if i hit into HTTPS Protocol. Am i missing something ?
I am already checking the proxy via browser, and it's working fine.
Thanks
Related
I have a request handler set up like this:
httpServer.addRequestHandler("^/send-contact-message", "./rest-extensions/contact-messages.js", "sendContactMessage");
I have CORS set up like this:
<cors enabled="true">
<domain name="imagesreimagined.com" methods="post"/>
</cors>
My server is set up with Secure Connections (HTTPS) set to Accept only HTTPS from remote & allow HTTP and HTTPS from localhost. If I send a request from a form with action="https://imagesreimagined.store/send-contact-message", I get an error in the browser stating:
XMLHttpRequest cannot load https://imagesreimagined.store/send-contact-message. Origin http://imagesreimagined.com is not allowed by Access-Control-Allow-Origin.
If I set my server’s Secure Connections (HTTPS) to Accept both HTTP and HTTPS connections and change the form action to http, it works. However, I need all remote connections to be https.
I also tried CORS with the 443 port and got the same error.
<cors enabled="true">
<domain name="imagesreimagined.com:443” methods="post"/>
</cors>
The server calling the Wakanda Server is not SSL, if that makes a difference.
Once I removed the port number from the cors domain name and added SSL to the server that hosts the website posting to the Wakanda Server, it worked.
I guess this is not an answer but rather adding more to the question in the hope it helps.
This is amazing. I logged into SO this morning intending to ask this very same question. My setup is very slightly different.
I have my Wakanda server set to accept only SSL connections and set to Accept only HTTPS from remote & allow HTTP and HTTPS from localhost. The Wakanda server is published on port 8443.
On the same machine I have an Apache server running on port 80 that publishes my Angular 2 app.
I spent several hours trying to get CORS to work with no success. I haven't tried running the Angular app on SSL yet, but that sounds like it would be worth a try.
=====================
After further investigation, I found the problem.
Don't include the protocol in the CORS definition.
ie:
Instead of
<domain name="http://app.example.com" methods="post;get;put;delete"/>
It should be:
<domain name="app.example.com" methods="post;get;put;delete"/>
Pretty obvious really but I didn't see it for a long time.
If UDP is blocked, i need to enable HTTP(s) fallback with aspera connect plugin thru HAProxy. Has anyone successfully done this ? I have read all the documentation but there is nothing that describes the HAProxy use case
I assume you talk about a client side forward proxy.
If you use the IBM Aspera Connect Client, it comes with HTTP (forward) proxy configuration.
http://download.asperasoft.com/download/docs/connect/3.9.6/user_osx/webhelp/index.html#dita/network_environment.html
This will work when the client falls back to HTTP.
Note that the client will fallback to HTTP only if this feature is enabled on the server side.
You can see that by examining the parameters provided to the client by the browser (put in dev mode). In that case, it has http parameters (port).
Typically, parameter: https_fallback_port
If not, then there is no possible http fallback, and it will not use the (forward) proxy.
If you are talking about reverse proxy in front of a server configured with fallback, this is part of the (public) documentation of the IBM Aspera Proxy.
I'm using Charles as a proxy to debug some HTTP requests. However, one of the endpoints is www.myendpoint.com:9064 and I need a proxy (myproxy.com:80) to access it. When I try to debug it with charles it fails to connect to that endpoint. Do I need to do any extra configuration for this case?
Charles Proxy automatically tries to configure your system's proxy (in Windows and macOS) so by this many applications, such as browsers, use it automatically.
By what you say in your comment, you seem to be developing an application, which I guess you configured to use the myproxy.com:80 proxy.
Being this the case, what you need to do is to configure your application to use the Charles Proxy, which usually opens up at your localhost:8888, instead of the myproxy:80.
This will make your application access the internet through the Charles proxy and thus your HTTP request will start to appear to the Charles overview window, but the requests will still not be able to reach www.myendpoint.com:9064.
To do so, you need to configure your proxy values (myproxy.com:80) on the External Proxy Settings (Proxy -> External Proxy Settings...) on Charles.
This will make Charles be able to reach your endpoint.
To access some websites that I need to test I need to plugin some specific proxies on firefox. However when I set my proxy through firefox or any browser, fiddler doesnt capture anymore request, due that it also uses its own proxy to get the requests. Is there any way I could capture traffic using fiddler while at the same time Im using an external proxy using any browser?
Fiddler allows you to chain to an upstream proxy, so traffic first goes to Fiddler, then goes from Fiddler to another proxy.
Fiddler will automatically chain to any proxy configured in Internet Explorer.
To manually chain to a different proxy, in Fiddler, click Tools > Fiddler Options and go to the Gateway tab. Specify the desired upstream proxy there.
I want to log all HTTP requests made by the browser to a file, so I thought I can run a HTTP/S proxy locally and do this. However, the proxies at proxies.xhaus.com/ don't meet my needs - either no HTTPS support or no logging. Do anyone of you know of a proxy that can do both HTTPS and HTTP and allow me to log the browser traffic to a file?
Squid can do that.
http://wiki.squid-cache.org/Features/SslBump
Squid was also my first thought given your description, but for development use you might prefer a more powerful intercepting proxy like:
Fiddler2
Paros Proxy
Burp Suite (despite the name, my personal favorite)