I've recently come accross an issue with IIS responding with a 410 status code when a request query string exceeds 500 characters.
The application is an asp.net web app using the classic managaged pipline.
I've already tried increasing the maxRequestLength, maxUrlLength, and maxQueryStringLength to their max of 2097151 to no avail.
I don't understand why the server would respond with a 410 status code.
Any help would or insight would be greatly appreciated.
Related
I am always getting status 429 through scrapy but then get status 200 when using browser for the same url. Is this a preventative measure by the domain to disallow scraping of their site or is it my setting?
As I know, status 429 is too many request. I have tried setting concurrent request to 1 and it's still not working.
Hope someone could give me some feedback on this.
Thanks all
Would you be able to share the domain you're attempting to scrape? This will help me debug your issue.
Thx
I have been working on an application that provides some web services to a client. The MVC application is built on .Net 4.5 framework. Everything worked fine until we looked at the response statistics our client had generated, where we could see we weren’t responding 100%. The statistics showed response drop to 90%-95% every other day.
Inspecting the logs
The first thing I did was to check our application log where I couldn’t find any exceptions logged. We log all (unhandled) exceptions in our application, which would normally lead to an error HTTP status code, so finding no such exception made me think that the request has not reached the application at all. The next step was to check the IIS access logs and there I could not find any 500 errors. I was under the impression that something is going on with the network which is causing 500's.
Upon further investigation, I realized those are being generated by IIS server. I found this by setting up Failed Request Tracing on IIS and after a while I found following error logged:
ModuleName - ManagedPipelineHandler Notification -
EXECUTE_REQUEST_HANDLER HttpStatus - 500 HttpReason - Error Retrieving
Data HttpSubStatus - 0 ErrorCode -The operation completed
successfully. (0x0)
I've looked at various stackoverflow posts but nothing really helped me. I guess it is because of no of requests we make per minute around 200 requests per minute). But I get response for 90-95% requests.
Attached detailed error log here
I figured out what the error is. .Net servers don't receive these requests in the first place, these are getting lost in the network. There is an oracle gateway which is buggy and killing few requests.
I have an api application which are givin me quite a headache. So in desperation I'm posting my problem here.
Short version
In short I need to know how I can debug my application to figure out what is causing the 500 Internal Server Error, I've tried to look into the Event log, but it doesn't tell me much besides which requests have failed, nothing about why they failed. So I honestly have no clue where to go from here.
The API is an ASP.Net MVC project and is hosted on an IIS 8.5 Windows Server 2012 R2
try sending a get request and reading the response. To get an increased level of error info, enable remote errors
https://technet.microsoft.com/en-us/library/bb684665.aspx
I am a beginner in ASP.NET Web Api. So i started with this small project from pluralsight. I had the project downloaded and the only problem is that whenever i started the web api and as soon as i entered some URL any (get or posts) the request goes in a never ending loop. I tried using the fiddler and saw something like this in the log.
05:04:40:9644 HTTPSLint> Warning: ClientHello record was 508 bytes
long. Some servers have problems with ClientHello's greater than 255
bytes.
https://github.com/ssllabs/research/wiki/Long-Handshake-Intolerance
05:04:40:9944 HTTPSLint> Warning: ClientHello record was 508 bytes
long. Some servers have problems with ClientHello's greater than 255
bytes.
The same message for all my api calls again and again from the browser.
Can anyone help me on this.. any help would be much appreciated..
Thanks
I have an application, written in C++.
This app dispatches a certain info to a script located on a remote website using HTTP POST requests. The app sends requests with a period from several seconds to several minutes.
The problem is that after about a half an hour of working without errors, the app starts to get a 408 Request timeout error from the web server. Then the app starts to retry posting but the server keeps on responding with 408 Request timeout.
An interesting observation: the error disappears after I access the website using a browser and the app works OK for about 30 minutes after that, then the issue comes back.
What could be the reason and is there any workaround to this?
PS: the app works on a usual PC with XP Workstation. The website is on GoDaddy web server.
thanks in advance
I know this is an old post but thought this might help someone since this problem cause me hours of frustration.
I was experiencing the same issue with a GoDaddy webserver. My Android app sent POST requests to the server and would work as expected but I started experiencing 408 Request timeout errors after 30 mins or so. I also noticed that the problem went away if I opened up a browser and opened my home page (PHP Wordpress site) from a PC or the Android device. The website was in test so web traffic was minimal and I was able to confirm this behaviour in the server logs fairly easily.
I logged a support call to GoDaddy but whilst their staff were responsive and helpful, they did not provide any useful information to explain the behaviour.
I was however able to work around the issue by simply executing a dummy GET request before my POST request and this 'woke up' the web server and it responded to all subsequent POST requests.