http.sys

What can cause Chrome to give an net::ERR_FAILED on cached content against a server on localhost?

佐手、 提交于 2021-02-06 14:27:48
问题 I'm building a web server and trying to test things. The server is running on localhost:888 , and the first time I load the web app, everything works. But if I try to reload the page, a bunch of XmlHttpRequest requests fail with net::ERR_FAILED . By putting breakpoints in the server code, I can verify that the requests are never actually coming in. This isn't a connection failure, as the connection succeeds the first time. The fact that it succeeds once and then fails later implies that it

What can cause Chrome to give an net::ERR_FAILED on cached content against a server on localhost?

此生再无相见时 提交于 2021-02-06 14:27:44
问题 I'm building a web server and trying to test things. The server is running on localhost:888 , and the first time I load the web app, everything works. But if I try to reload the page, a bunch of XmlHttpRequest requests fail with net::ERR_FAILED . By putting breakpoints in the server code, I can verify that the requests are never actually coming in. This isn't a connection failure, as the connection succeeds the first time. The fact that it succeeds once and then fails later implies that it

What can cause Chrome to give an net::ERR_FAILED on cached content against a server on localhost?

孤人 提交于 2021-02-06 14:26:49
问题 I'm building a web server and trying to test things. The server is running on localhost:888 , and the first time I load the web app, everything works. But if I try to reload the page, a bunch of XmlHttpRequest requests fail with net::ERR_FAILED . By putting breakpoints in the server code, I can verify that the requests are never actually coming in. This isn't a connection failure, as the connection succeeds the first time. The fact that it succeeds once and then fails later implies that it

What can cause Chrome to give an net::ERR_FAILED on cached content against a server on localhost?

℡╲_俬逩灬. 提交于 2021-02-06 14:25:49
问题 I'm building a web server and trying to test things. The server is running on localhost:888 , and the first time I load the web app, everything works. But if I try to reload the page, a bunch of XmlHttpRequest requests fail with net::ERR_FAILED . By putting breakpoints in the server code, I can verify that the requests are never actually coming in. This isn't a connection failure, as the connection succeeds the first time. The fact that it succeeds once and then fails later implies that it

What can cause Chrome to give an net::ERR_FAILED on cached content against a server on localhost?

落爺英雄遲暮 提交于 2021-02-06 14:25:15
问题 I'm building a web server and trying to test things. The server is running on localhost:888 , and the first time I load the web app, everything works. But if I try to reload the page, a bunch of XmlHttpRequest requests fail with net::ERR_FAILED . By putting breakpoints in the server code, I can verify that the requests are never actually coming in. This isn't a connection failure, as the connection succeeds the first time. The fact that it succeeds once and then fails later implies that it

Do web.config header size limits override http.sys limits in the registry?

霸气de小男生 提交于 2021-01-01 04:28:45
问题 I have an ASP.Net 4.0 application using Windows Integrated Authentication on IIS7.5 on Windows 2003. Some users are reporting errors with this message: Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long. Others succeed in loading pages but have errors loading other resources and performing AJAX calls. One of the users experiencing intermittent errors has a Kerberos Authorization header of about 5700 characters. This user is a member of 250 AD groups. My

Do web.config header size limits override http.sys limits in the registry?

一个人想着一个人 提交于 2021-01-01 04:27:06
问题 I have an ASP.Net 4.0 application using Windows Integrated Authentication on IIS7.5 on Windows 2003. Some users are reporting errors with this message: Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long. Others succeed in loading pages but have errors loading other resources and performing AJAX calls. One of the users experiencing intermittent errors has a Kerberos Authorization header of about 5700 characters. This user is a member of 250 AD groups. My

Do web.config header size limits override http.sys limits in the registry?

我们两清 提交于 2021-01-01 04:26:47
问题 I have an ASP.Net 4.0 application using Windows Integrated Authentication on IIS7.5 on Windows 2003. Some users are reporting errors with this message: Bad Request - Request Too Long HTTP Error 400. The size of the request headers is too long. Others succeed in loading pages but have errors loading other resources and performing AJAX calls. One of the users experiencing intermittent errors has a Kerberos Authorization header of about 5700 characters. This user is a member of 250 AD groups. My

安全狗:HTTP.SYS远程执行代码漏洞分析 (MS15-034 )

断了今生、忘了曾经 提交于 2020-12-18 00:52:57
【作者:安全狗安全研究团队】 写在前言: 在2015年4月安全补丁日,微软发布了11项安全更新,共修复了包括Microsoft Windows、Internet Explorer、Office、.NET Framework、Server软件、Office Services和Web Apps中存在的26个安全漏洞。其中就修复了HTTP.sys 中一处允许远程执行代码漏洞,编号为:CVE-2015-1635(MS15-034 )。目前 服务器安全 狗已经更新了安全补丁,建议及时修复安全狗提示给您的漏洞信息,以免漏洞被利用遭到攻击。 据称,利用 HTTP.sys的安全 漏洞,攻击者只需要发送恶意的http请求数据包,就可能远程读取IIS服务器的内存数据,或使服务器系统蓝屏崩溃。 根据公告显示,该漏洞对服务器系统造成了不小的影响,主要影响了包括Windows 7、Windows Server 2008 R2、Windows 8、Windows Server 2012、Windows 8.1 和 Windows Server 2012 R2在内的主流服务器操作系统。 安全狗安全研究团队的小伙伴们在得知这一漏洞情况后,也对其进行了深入挖掘研究,下面就将相关信息结果分享给大家。如果有任何想法,以及进一步的利用操作,也欢迎指教讨论。 1. 首先对补丁文件做了二进制比对 以下是Windows 7

How are threads tied to requests through Http.sys, IIS and ASP.NET

非 Y 不嫁゛ 提交于 2019-12-29 14:16:17
问题 I'm currently reading a lot about node.js. There is a frequent comparison between servers using a traditional thread per request model (Apache), and servers that use an event loop (Nginx, node, Tornado). I would like to learn in detail about how a request is processed in ASP.NET - from the point it is received in http.sys all the way up to it being processed in ASP.NET itself. I've found the MSDN documentation on http.sys and IIS a little lacking, but perhaps my google-fu is weak today. So