This is the same exact problem as a previously unanswered question:
CFHTTP and IIS 7 Connection Failture (NOT SSL)
On IIS7 + CF9 on Win7, CFHTTP POST fails with a HTTP Error 408 Request Time-out most of the time when using CFHTTP on localhost on port 80 without SSL. It is successful about 5% of the time (or less), meaning intermittently it will get processed. But most of the time it just fails.
The address I call is:
http://localhost/integration/MY_KFKPortal/index.cfm?svc=KFKIncoming_MRC
which works fine from the browser. My CFHTTP code is:
<cfhttp url="#URL#" method="POST" result="objGet" timeout="20" throwOnError="no">
<cfhttpparam name="Content-Type" type="HEADER" value="content-type:text/html;charset='UTF-8';">
<cfhttpparam type="body" value="#PostString#"/>
</cfhttp>
Anyone found the solution to this problem?
It should be two consideration for this case.
how about removing throwonerror attribute from your cfhttp tag.
check your firewall, router and other network for blocking cfhttp port.
Related
My program sends http requests to https://auth.riotgames.com/api/v1/authorization server. As I understand it, cloudflare is installed there, which blocks my requests by issuing a 403 status code.
But the problem is that if I run the Http Debugger (https://www.httpdebugger.com/) the server responds fine. This is independent of the use of a proxy. Might have something to do with the certificates as I tried to connect with Fiddler installed on another machine (with Http Debugger running on my machine) and if Fiddler decrypts the http traffic it starts responding with 403, and if it doesn't decrypt it responds fine.
With Http Debugger:
With Http Debugger and Fiddler on another machine:
If it's not clear, ask questions. I will be glad to any suggestions, for me it is very important.
I am trying to use Postman to make some requests to my API and the problem is that always I get a 404 response even when the browser gives me a 200.
Here is my Postman request:
It's very confusing. How could I fix that? Is there a problem with Postman, my Apache, my PHP?
Working with xampp (PHP 7.1.1) and the desktop version of Postman.
Update #1:
The problem seems to be the Postman as it is sending the request via proxy even with that option disabled.
When I send a request to google.com.cu all works fine (it shouldn't be because my connection is behind a proxy and Postman don't know that config).
After that, I unplugged my network, and Postman was not been able to send more requests (all good for external requests) but not for my localhost.
Does Postman need an internet connection to send localhost requests?
Update #2:
The server browser response is OK (symfony welcome page).
I can see in your request that you don’t supply a port number, just localhost and then the route - Is this intentional?
You could try just localhost:<port>/<your_route>
These are both timeout errors, but who is timing out in a 408 vs. a 504?
From w3, 408 is defined as:
The client did not produce a request within the time that the server was prepared to wait. The client MAY repeat the request without modifications at any later time.
...And 504 is:
The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI (e.g. HTTP, FTP, LDAP) or some other auxiliary server (e.g. DNS) it needed to access in attempting to complete the request.
So who is the 'client' in the 408 if not an intermediary server? If it's an actual end user, how does a server know to wait for their request before they have made it?
The client is the browser or client application. The server knows to wait for a request because it has accepted a connection, or already read part of the request, say a header or two.
Amazon documentation tells: http://docs.aws.amazon.com/en_en/elasticloadbalancing/latest/classic/ts-elb-error-message.html#ts-elb-errorcodes-http408
Indicates that the client cancelled the request or failed to send a full request
Mozilla documentation tells: https://developer.mozilla.org/en/docs/Web/HTTP/Status/408
The HTTP 408 Request Timeout response status code means that the server would like to shut down this unused connection. It is sent on an idle connection by some servers, even without any previous request by the client
Got a problem with squid. I'm using 3.1 version with my own redirector.
My problem was when a client for example request https://twitter.com (with https) but somehow got a logic with my redirector that twitter.com is invalid page so i redirected this request to my invalid page. Let say 302:http://mydomain.com?invalid=twitter.com, in this stage process will not continue and browser will say "HTTP gateway failed".
So, my theory is when a request is https redirected to http, squid will not work. Is there any configuration i need to be done so that it will work?
Thank you guys..
RFC 2817 isn't very clear about the behavior of CONNECT and redirect. I think that most of the browser won't accept a redirect as a reply to the CONNECT method. So, there is no way to do what you want.
Is not an Squid issue, is a protocol/browser issue.
well, i think the best way to redirect is when:
- if the request is https the response should be https
- and if the request if http response should be http
that's the best way i can't think at the moment...
I've been accessing Plesk Admin for a while at http://yourarthere.net:8443 but since I moved to a new home and ISP (Comcast) I am unable to get to the page using a browser or UNIX wget.
# wget http://yourarthere.net:8443
--2011-08-22 21:13:06-- http://yourarthere.net:8443/
Resolving yourarthere.net (yourarthere.net)... <IP>
Connecting to yourarthere.net (yourarthere.net)|<IP>|:8443...
connected.
HTTP request sent, awaiting response... ^C <canceled>
I can however access the page using my phone or another ISP.
The strange thing is that I can access the page from my home if I use a secure connection. I've been told that Plesk should forward to https automatically from http anyway but it isn't for some reason from my ISP (Comcast).
In addition, a second, possibly related issue, is that I am receiving a message that there is a problem with my security certificate. But again, it only happens when I connect from my ISP.
# wget https://yourarthere.net:8443/
--2011-08-23 14:02:40-- https://yourarthere.net:8443/
Resolving yourarthere.net (yourarthere.net)... 69.64.52.141
Connecting to yourarthere.net (yourarthere.net)|69.64.52.141|:8443... connected.
ERROR: cannot verify yourarthere.net’s certificate, issued by “/C=US/ST=Arizona/L=Scottsdale/O=GoDaddy.com, Inc./OU=http://certificates.godaddy.com/repository/CN=Go Daddy Secure Certification Authority/serialNumber=07969287”:
Self-signed certificate encountered.
To connect to yourarthere.net insecurely, use ‘--no-check-certificate’.
Here is the result from a colleague's attempt from a different ISP:
# wget http://yourarthere.net:8443
--2011-08-23 14:41:53-- http://yourarthere.net:8443/
Resolving yourarthere.net... 69.64.52.141
Connecting to yourarthere.net|69.64.52.141|:8443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://yourarthere.net:8443/ [following]
--2011-08-23 14:41:53-- https://yourarthere.net:8443/
Connecting to yourarthere.net|69.64.52.141|:8443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: `index.html.2'
The problem was due to a misconfigured SSL on the server which caused an error in the forwarding process. Problem fixed now.