blocks|key|3144739|text|CheckUpDown有a+nice+explanation+of+the+504+error|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3144740|服务器(不一定是网络服务器)充当网关或代理，以满足客户端(例如，您的网络浏览器或我们的CheckUpDown+robot)访问所请求的|3144741|的请求。此服务器没有收到它访问的处理您的HTTP请求的上游服务器的及时响应。|blockquote|3144742|3144743|这通常意味着上游服务器关闭(没有对网关/代理的响应)，而不是上游服务器和网关/代理没有就交换数据的协议达成一致。|3144744|此问题完全是由于后端计算机之间的IP通信缓慢造成的，可能包括Web服务器。只有在托管网络服务器的站点上设置网络的人员才能解决此问题。|3144745|entityMap|0|LINK|mutability|MUTABLE|url|http://www.checkupdown.com/status/E504.html^0|C|Z|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@$A|W|B|X|1|Y]]|C|$]]|$1|D|3|E|5|6|7|Z|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|10|8|@]|9|@]|C|$]]|$1|I|3|-4|5|6|7|11|8|@]|9|@]|C|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|C|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@]|C|$]]|$1|N|3|-4|5|6|7|14|8|@]|9|@]|C|$]]]|O|$P|$5|Q|R|S|C|$T|U]]]]

CheckUpDown has <a href="http://www.checkupdown.com/status/E504.html" rel="noreferrer">a nice explanation of the 504 error</a>:
<blockquote>
A server (not necessarily a Web server) is acting as a gateway or proxy to fulfil the request by the client (e.g. your Web browser or our CheckUpDown robot) to access the requested URL. This server did not receive a timely response from an upstream server it accessed to deal with your HTTP request.
This usually means that the upstream server is down (no response to the gateway/proxy), rather than that the upstream server and the gateway/proxy do not agree on the protocol for exchanging data.
This problem is entirely due to slow IP communication between back-end computers, possibly including the Web server. Only the people who set up the network at the site which hosts the Web server can fix this problem.
</blockquote>

blocks|key|3357519|text|你不能。问题不是你的应用程序没有耐心并且超时；问题是中间代理没有耐心并且超时。“服务器在充当网关或代理时，没有从URI指定的上游服务器收到及时的响应。”(http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.5)它很可能表示源服务器出现了某种问题，因此它不能快速响应转发的请求。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|3357520|可能的解决方案，没有一个可能会让你满意：|3357521|3357522|增加代理的超时值(如果在您的控制之下)|unordered-list-item|3357523|向另一台服务器发出请求(如果有另一台服务器具有相同的数据)|3357524|以不同的方式发出请求(如果可能)，以便一次请求的数据较少|3357525|一旦服务器没有问题，请重试|3357526|3357527|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.5^0|25|1S|0|0|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|Y|8|@]|9|@$A|Z|B|10|1|11]]|C|$]]|$1|D|3|E|5|6|7|12|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|13|8|@]|9|@]|C|$]]|$1|G|3|H|5|I|7|14|8|@]|9|@]|C|$]]|$1|J|3|K|5|I|7|15|8|@]|9|@]|C|$]]|$1|L|3|M|5|I|7|16|8|@]|9|@]|C|$]]|$1|N|3|O|5|I|7|17|8|@]|9|@]|C|$]]|$1|P|3|-4|5|6|7|18|8|@]|9|@]|C|$]]|$1|Q|3|-4|5|6|7|19|8|@]|9|@]|C|$]]]|R|$S|$5|T|U|V|C|$W|X]]]]

You can't. The problem is not that your app is impatient and timing out; the problem is that an intermediate proxy is impatient and timing out. "The server, while acting as a gateway or proxy, did not receive a timely response from the upstream server specified by the URI." (<a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.5">http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.5.5</a>) It most likely indicates that the origin server is having some sort of issue, so it's not responding quickly to the forwarded request.

Possible solutions, none of which are likely to make you happy:

<ul>
<li>Increase timeout value of the proxy (if it's under your control)</li>
<li>Make your request to a different server (if there's another server with the same data)</li>
<li>Make your request differently (if possible) such that you are requesting less data at a time</li>
<li>Try again once the server is not having issues</li>
</ul>

blocks|key|3144791|text|如果您使用的是ASP.Net+5(现在称为ASP.Net核心v1)，请确保在您托管的每个站点的project.json“命令”部分中，不同站点之间的project.json代理侦听端口不同，否则一个站点将工作，但另一个将返回504网关超时。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3144792|+"commands":+{
++++"web":+"Microsoft.AspNet.Server.Kestrel+--server.urls+http://localhost:5090"
++},|code-block|syntax|javascript|3144793|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

If your using ASP.Net 5 (now known as ASP.Net Core v1) ensure in your project.json "commands" section for each site you are hosting that the Kestrel proxy listening port differs between sites, otherwise one site will work but the other will return a 504 gateway timeout.

<pre><code> "commands": {
 "web": "Microsoft.AspNet.Server.Kestrel --server.urls http://localhost:5090"
 },
</code></pre>

blocks|key|3357603|text|关于这个错误，我观察到的一件事是，只有来自服务器的第一个响应才会出现，在http的情况下，这应该是握手响应。一旦将即时响应从服务器发送到网关，如果主响应花费时间，则不会给出错误。这里的关键是服务器对请求的第一个响应应该是快速的。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3357604|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

One thing I have observed regarding this error is that is appears only for the first response from the server, which in case of http should be the handshake response. Once an immediate response is sent from the server to the gateway, if after the main response takes time it does not give an error. The key here is that the first response on a request by a server should be fast.

blocks|key|3144868|text|假设访问代理服务器A(例如，nginx)，并且服务器A将该请求转发到另一服务器B(例如，tomcat)。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3144869|如果此过程持续很长时间(超过代理服务器读取超时设置)，A仍未获得B的完整响应。|3144870|对于nginx，你可以配置proxy_read_timeout(in+location)属性来解决his.But，如果你把这个值设置得太高，这通常不是一个好主意。这可能隐藏了真正的错误。你最好改进设计才能真正解决这个问题。|3144871|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

Suppose access a proxy server A(eg. nginx), and the server A forwards the request to another server B(eg. tomcat). 

If this process continues for a long time (more than the proxy server read timeout setting), A still did not get a completed response of B.
It happens.

for nginx, You can configure the proxy_read_timeout(in location) property to solve his.But this is usually not a good idea, if you set the value too high. This may hide the real error.You'd better improve the design to really solve this problem.

blocks|key|3144882|text|我有另一个问题，给了我504分。这是相当遥远的，但我将它写在这里，为谷歌人和后代…|type|unstyled|depth|inlineStyleRanges|entityRanges|data|3144883|我有一个客户端调用另一个域(Active+Directory)中承载的IIS托管IIS服务。客户端域和承载web服务的域之间不存在完全信任。这两个域之间选择性信任的众多挑战之一是，当从一个域调用到另一个域时，Kerberos无法工作。|3144884|在我的例子中，我试图调用另一个域中的服务，在那里我发现注册了一个SPN。如下所示:+http/myurl.test.local+(只是一个示例)|3144885|这迫使调用使用Kerberos，而不是让它回退到NTLM，这使我从调用服务器返回了405。|3144886|删除spn并允许调用回退到NTLM后，它可以正常工作。|3144887|如我所说..。这不是你可能会遇到的事情，因为大多数组织不会冒险在两个域之间建立这样的选择性信任……但它给出了504，并使我有一些(更多)的白发。|3144888|entityMap^0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|P|8|@]|9|@]|A|$]]|$1|F|3|G|5|6|7|Q|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|R|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|S|8|@]|9|@]|A|$]]|$1|L|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|M|$]]

I have had another issue giving me a 504. It's pretty far out but I'll write it up here for googlers and posterity...

I have a client calling an IIS hosted webservice hosted in another domain (Active Directory). There is not full trust between the client domain and the domain where the web services is hosted. 
One of the many challenges with the selective trust between these two domains is that Kerberos does not work when calling from one to the other.

In my case I was trying to call a service in another domain where I found out that a SPN was registered. Like this : http/myurl.test.local (just an example)

This forces the call to use Kerberos instead of letting it fall back to NTLM and this gave me a 405 back from the calling server. 

After removing the spn and allowing the call to fall back to NTLM, it works fine.

As I said ... this is not something you are likely to run into, as most organizations do not venture into having such a selective trusts between two domains ... But it gives a 504 and caused me a few (more) gray hairs.

I'm getting the following error when my win32 (c#) app is calling web services.
<pre><code>The request failed with HTTP status 504: Gateway timeout server response timeout.
</code></pre>
I understand 'I think' that this is because the upstream request does not get a response in a timely fashion.
But my question is this? How do I change the app.config settings in my win32 application to allow more time to process its data. I assume I require these changes to be made on my app settings as the webservices and IIS hosting the ws are setup with extended times.
Look forward to a response and thank you in advance.

HTTP Status 504

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

当我的win32 (c#)应用程序调用web服务时，我收到以下错误。The request failed with HTTP status 504: Gateway timeout server response timeout.我理解“我认为”这是因为上游请求没有得到及时的响应。但我的问题是？如何更改win32应用程...

问HTTP状态504
EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTTP状态504EN

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问HTTP状态504
EN