HTTP状态902-没有此类对话 [英] HTTP Status 902 - No such conversation

查看:433
本文介绍了HTTP状态902-没有此类对话的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我正在和一位同事一起做一些工作,涉及将回调URL从我的模块传递给他.由于他方面的一些错误配置,因此回调URL有所不同,它从他的服务器而非我的服务器中调用了URL. Appart修复了该错误,在配置错误的回调过程中,我收到了此响应(这是我之前从未见过):

I was working with a colleague doing some work that involves passing callback URL's from my module to his. Because of some misconfiguration on his side, the call back URL was different and it called a URL from his server, not mine. Appart that we fixed the error, during that misconfigured callback I got this response (which I've never seen before):

HTTP Status 902 - No such conversation

出于好奇,我四处搜寻,找不到此HTTP状态代码的任何规范或描述,而且我一直认为状态代码仅从1XX到5XX(如

Just out of curiosity I googled around and can not find any specification or description of this HTTP status code, and I always thought that status codes only went from 1XX to 5XX (As explained in Section 10 of the HTTP 1.1 Spec)

有什么想法可以在哪里找到描述此规范的官方(或没有)规范?

Any idea where I can find an official (or not) spec that describes this?

仅供参考,该服务器是Tomcat 7.0.25

FYI the server in question is a Tomcat 7.0.25

编辑:包括回复图片

推荐答案

很抱歉,但是事实证明,负责此工作的是内部公司库的重用,因此与之无关Tomcat,也不是Spring,也不是任何东西.它只是公司专有的响应代码.

Sorry for all the buzz but it turned out that a re-used internal company library is the one responsible for this, so it is NOT related to Tomcat, nor Spring nor anything. It is simply a proprietary company response code.

这篇关于HTTP状态902-没有此类对话的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆