HTTP 404.15错误 – 未找到…因为查询字符串太长

huangapple go评论60阅读模式
英文:

Getting HTTP 404.15 Error - Not Found ...because the query string is too long

问题

我正在从服务器获取信息。从服务器接收到的SAML响应中使用了GET方法,导致出现错误:

查询字符串过长,导致HTTP错误404.15,未找到。

我尝试从IDP(身份提供者)获取SAML响应,该IDP执行身份验证并在成功身份验证后将我重定向到页面。我接收到的是GET方法类型的SAML响应,由于查询字符串的长度,导致出现HTTP错误404.15未找到的消息。

我想知道是否有一种安全的方法可以解决这个问题。

英文:

I'm fetching the information from the server. The get method is being used in the SAML Response I'm receiving from the server, which is producing an error:

The query string is too long, resulting in HTTP Error 404.15, not found.

I have attempted to obtain a SAML response from the IDP (identity provider) that performs the authentication and directs me to the page upon successful authentication. What I am receiving is a SAML response of the Get method type, which produces the HTTP Error 404.15 not found message due to the length of the query string.

I want to know whether there is a secure way for me to go around this problem.

答案1

得分: 1

IdP应该通过HTTP Post发送SAML响应。SAML规范不支持将SAML响应作为查询字符串参数发送,这正是你所看到的原因。

英文:

The IdP should send the SAML response in an HTTP Post. The SAML specification doesn't support sending the SAML response as a query string parameter for the very reason you're seeing.

huangapple
  • 本文由 发表于 2023年2月6日 17:31:34
  • 转载请务必保留本文链接:https://go.coder-hub.com/75359498.html
匿名

发表评论

匿名网友

:?: :razz: :sad: :evil: :!: :smile: :oops: :grin: :eek: :shock: :???: :cool: :lol: :mad: :twisted: :roll: :wink: :idea: :arrow: :neutral: :cry: :mrgreen:

确定