New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Empty Response and Response Code #477
Comments
Have you tried updating the local libcurl ? Are you able to pin point the issue maybe to an HTTPS sites? I am asking this because of the |
Here is some information that might help:
|
7.15.5 was released on August 7 2006, I would suggest to try and update to a newer version, there has been so much going on since. Not that it's a sure fix, but since I don't remember seeing this behaviour before + don't remember anyone using that old of a version - it does seem a likely correlation. |
This is probably because you have configured a cache strategy so Typhoeus is caching the first request and returning the result in the subsequent requests. I'm having the same problem but the request is a POST request which should be not cached by Typhoeus. Any thoughts? |
I dont have a cache strategy configured. I also added a unique id to the url in order to bypass any caching as a test and this did not have any effect. |
|
BTW, I just ran into this with a site I'm working on. Just bought a new SSL cert for ChartURL.com and forgot to add the intermediate certs when I added the site to my nginx proxy. |
I have some code that makes a request, the first request succeeds and then all subsequent requests return an empty result.
For example:
Typhoeus.get("http://google.com")
I thought it might have been caching so I added a UUID to the url as a parameter, but this did not fix the problem.
This is a server (uat), so after every deploy it works once. My local environment works without this problem.
The text was updated successfully, but these errors were encountered: