Jenkins 2.192:HTTP错误403:请求中未包含有效碎屑 [英] Jenkins 2.192: HTTP Error 403: No valid crumb was included in the request

查看:399
本文介绍了Jenkins 2.192:HTTP错误403:请求中未包含有效碎屑的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我最近升级到Jenkins 2.192,我的应用程序开始失败并出现以下错误:

I recently upgraded to Jenkins 2.192, and my applications started failing with the following error:

HTTP Error 403: No valid crumb was included in the request
Reason: No valid crumb was included in the request

降级到Jenkins 2.189后,我看不到问题. 我看不到詹金斯2.189、2.190、2.191的问题. 我遇到了詹金斯2.192(也见2.196)的问题

I do not see the problem after downgrading to Jenkins 2.189. I do not see the issue with Jenkins 2.189, 2.190, 2.191. I hit the issue with Jenkins 2.192 (also seen with 2.196)

2.191和2.192之间发生了某些变化,导致了我观察到的故障.

SOMETHING CHANGED BETWEEN 2.191 AND 2.192 , causing the failure I observed.

推荐答案

一种无需更改源代码的简单解决方案(已通过Jenkins v2.222验证):

A simple solution without need of making changes to source code (validated with Jenkins v2.222):

  1. 安装Strict Crumb Issuer插件( https://plugins.jenkins.io/strict- crumb-issuer/)
  2. 启用此插件,然后从其配置中取消选中检查会话ID"(在Jenkins配置全局安全性下)

缺点是此解决方案使我们依赖于Strict Crumb Issuer插件,并删除了安全性功能.但是,由于我们的应用程序需要许多其他插件,并且只能在没有Internet访问的防火墙后运行,因此可以接受.

A drawback is that this solution makes us dependent on the Strict Crumb Issuer plugin and removes a security feature. But since our application requires many other plugins and only runs behind the firewall without Internet access, this is acceptable.

这篇关于Jenkins 2.192:HTTP错误403:请求中未包含有效碎屑的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

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