Unauthorized error when surfing to files - http

My IIS is configured to use WindowsAuthentication.
When I surf to the file:
I can see the file perfectly but when i'm checking with charles (http debugger) I see the following result.
alt text http://img155.imageshack.us/img155/6428/capturea.jpg
The problem is that when a browser does this, it will retry (apperantly up to 3 times) but when .NET (spring.net) tries this, it's crashes after the first attempt saying that I'm unauthorized.
Does anyone has a solution for this? I've been struggeling with this problem for weeks now.

I see this is normal. You may learn more about the conversation between client and server from this KB article,
http://support.microsoft.com/kb/264921
Then you will know why those 401 messages were there.
Regards,

Related

how do I fix ngrok invalid HTTP response error

I am using zphisher. when i create a link to ngrok, the link is generated, but on opening it it says ngrok gateway error The server returned an invalid or incomplete HTTP response. I got to know from ngrok error documentation that it is error 3004. they tell the error code and message but no possible way to fix the error. can someone help me please. I think my brother watches YouTube during his online classes and I want to conform it. No phishing. Please. I got absolutely no help from anywhere. Just one of my friend told me that i need an ngrok account for that. tried it, doesn't work.
After some time I got it fixed doing 2 things:
Make sure my local site is http (not https)
Running command ngrok http -host-header=rewrite localhost:PORT
For me, this command worked when I was receiving the 3004 error message and trying to access HTTPS on https://localhost:3000:
./ngrok http https://localhost:3000
If your site using https://localhost:port
below really works for me
ngrok http https://localhost:port --host-header=rewrite
I found an answer in this link and it solved my problem.
According to this you can use this command instead:
ngrok http https://localhost:[port]

"Your request could not be processed" error in IIS application

An asmx service we're hosting under IIS decided to attach below message at the top of xml response body rendering the xml invalid. The guid is unique in each response.
Your request could not be processed. Please press the back button on
your browser and try again. If the problem persists, please contact
technical support. Information below is for technical support:
Support Code: 7d6cbea0-9491-4cb0-9ca0-32f0a8b41bc4
I've limited access to the source; it does not appear like this is coming from the application code itself. Googling brings several hits current or cached having exactly the same behavior (variation of "could not processed" or "could not be processed" in different cases):
https://www.histiocure.org/jTlSn/about.aspx
https://webcache.googleusercontent.com/search?q=cache:8gRsTgrCarQJ:https://retirement.insperity.com/education.aspx+&cd=4&hl=en&ct=clnk&gl=us
https://www.perfectprovisions.org/index.aspx
Yet, I don't get any hit from technical sites like stackoverflow or MSDN. This is very puzzling; has anyone seen this behavior? Is it IIS doing this? What causes this?
BTW, the issue itself was resolved when AppPool was restarting but I'm worried that this can happen again anytime unless we get to the bottom of this.

XMLHttpRequest Internal Server Error 500 Debugging

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

ASP.NET debugger gives errors with http, while working with https

I really desperately need your help because I got very unusual problem with my programs:
I am receiving this error when I am trying to debug my ASP.NET or MVC Application on local IIS Server 7.5:
"Unable to start debugging on the web server. The debug request could not be processed by the server due to invalid syntax. "
I tried literally every solution I could find in google until this day. I spent 12 hours trying to figure this out. Without luck.
Error happens only with this address: http:// localhost/AspDemo not with this one: https:// localhost/AspDemo. Basically, I can debug like always if I put https instead of http.
https is disabled on my local IIS server :), I mean it is set to ignore.
Moreover I CAN open my sites with using BOTH protocols in IIS Control Panel
If I disable ASP.NET Debugger in Properties of my App in Visual Studio, Application runs fine.
This is the error from the httperr log:
2014-10-30 00:23:46 ::1%0 2977 ::1%0 80 - - - 400 - Verb -
I am not sure where exactly, but in some other log I saw reference to something like this: Error 400 "Bad Request - Invalid Verb"
A week ago ALL applications I got problems with were working perfectly with asp.net debugger from visual studio, I had no idea what happened.
I suspect some update. Because updates lately messed with my custom bootloader as well.
When I enable tracing - log is empty with http
Fiddler log is empty as well, maybe there is some config I can use in Fiddler to produce some more logs? (It logs of course with modified machine.config when I use https)
Would be eternally grateful for your help, if you need some more logs, please don't hestitate to ask.
I would like to mention as well that yes, I saw similar posts on this site, but none of them described problem this similar to mine.
/edit
From what I was able to observe, error happens BEFORE debugger access machine.config file, can you guys tell me how to catch errors in that moment?
==== /edit 2 ====
Anyone? No one knows the answer?
Recently I was able to find the complete error message in: C:\Users\\AppData\Local\Temp\Visual Studio Web Debugger.log
http://localhost/MVCDemo/debugattach.aspx
Status code=400 (Bad Request)
Protocol version=1.1
Cached=False
Connection=close
Content-Length=326
Content-Type=text/html; charset=us-ascii
Date=Fri, 31 Oct 2014 03:44:14 GMT
Server=Microsoft-HTTPAPI/2.0
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid Verb</h2>
<hr><p>HTTP Error 400. The request verb is invalid.</p>
</BODY></HTML>
In proccess monitor, I found this one as well:
<event>
<ProcessIndex>1339</ProcessIndex>
<Time_of_Day>04:40:33,3661553</Time_of_Day>
<Process_Name>devenv.exe</Process_Name>
<PID>10768</PID>
<Operation>CreateFile</Operation>
<Path>C:\Users\<UserName>\AppData\Roaming\Microsoft\VisualStudio\12.0\Debugger\StepIntoFilterData.ini</Path>
<Result>PATH NOT FOUND</Result>
<Detail>Desired Access: Read Data/List Directory, Read Attributes, Synchronize, Disposition: Open, Options: Sequential Access, Synchronous IO Non-Alert, Non-Directory File, Attributes: n/a, ShareMode: Read, Delete, AllocationSize: n/a</Detail>
</event>
I really, really need help with this.
=== /edit 3 ===
Second error is not relevant, I just checked and it is present with https as well (C:\Users\\AppData\Roaming\Microsoft\VisualStudio\12.0\Debugger\StepIntoFilterData.in), and debugging as https localhost works perfectly.
=== /edit 4 ===
Here are Process Monitor logs captured during Visual Studio Debugging HTTP (not working) and HTTPS (working)
(Test performed on random MVC Tutorial)
Use CTRL+F and Look for "Visual Studio Web Debugger.log" in logs to get the idea when it is happening. In https log is good, in http log returns Invalid Verb error mentioned before.
HTTP (not working)::
https://www.dropbox.com/s/7b26ybogtyqlico/LogFile%20HTTP%20NOT%20Working.CSV?dl=0
HTTPS (working):
https://www.dropbox.com/s/ggsj57v97ky90e6/LogFile%20HTTPS%20Working.CSV?dl=0
I might be wrong, but I think the key here is that only HTTP doesn't work and only with VS Debugger, everything else is just fine (HTTP and HTTPS without debugging and HTTPS with debugging.)
(It happens with every solution on IIS, new ones are affected too, all of these solutions were working, moreover some of them were not even changed from the time they have been working, IIS config didn't change as well)
I do not see the name of the verb in any of the description here, but my guess is VS debugger using a special verb (DEBUG) rather than the standard GET, HEAD, POST, etc. If you re-installed IIS after VS, the ISAPI mapping probably got nuked. This may solve the problem:
https://msdn.microsoft.com/en-us/library/ms165022%28v=vs.90%29.aspx

Fiddler: Error 502 Proxy Error

I am using Fiddler to debug all HTTP request of my ASP.NET application.
For a while (about 6 months) I had no problem. All HTTP requests appeared on Fiddler and so on.
The last two days Fiddler stoped working :/ Always returns the same error: "The request failed with HTTP status 502: Proxy Error ( The ISA Server denied the specified Uniform Resource Locator (URL). )."
The strange thing is that only happens to my application, i. e. all HTTP requests from youtube, email, etc, appear on Fiddler.
What is the problem here?
From my case adding this line on OnBeforeRequest function in Fiddler Script fixed it for me,
oSession["x-OverrideSslProtocols"] = " ssl3;tls1.0;tls1.1;tls1.2";
I had the same issue with Fiddler - my HTTPS site worked fine in IE, however got 502 error in Chrome. After analyzing the issue, I found that has manual proxy enabled in Fiddler (not recommended):
Tools -> Fiddler Options -> Gateaway
it was the root cause of this strange behavior. Switching to "System Proxy" made this working for both IE and Chrome.
I had a scenario where production url was https and test was http.
When wrongly calling test with https in fiddler then I got 502 and ended here on stack overflow.
I will just leave this here in case anyone else does the same mistake.
I solved my problem =)
I seems that something changed at my company network. So I changed the file CustomRules.js from Fiddler and added some lines at OnBeforeRequest.
Now, everything works just fine
Best regards.

Resources