Ah, I see. Thank you.
Hoping I can easily find the way to revert it via commits history. We're
not worried about the security issue, just the functionality.
On Thursday, May 19, 2022 at 3:46:53 AM UTC-5 db...@cloudbees.com wrote:
> On Wed, May 18, 2022 at 10:02 PM adam.l...@gmail.com
>
On Wed, May 18, 2022 at 10:02 PM adam.l...@gmail.com <
adam.l.lev...@gmail.com> wrote:
> But the way I read that is as a warning: subject to CSRF problems, be
> warned. I don't see any indication that GET has been disabled.
>
> What am I not seeing?
>
With publication of the advisory, we suspen
Thank you for that.
But the way I read that is as a warning: subject to CSRF problems, be
warned. I don't see any indication that GET has been disabled.
What am I not seeing?
Thank you
On Wednesday, May 18, 2022 at 2:48:31 PM UTC-5 db...@cloudbees.com wrote:
> On Wed, May 18, 2022 at 9:01
On Wed, May 18, 2022 at 9:01 PM adam.l...@gmail.com
wrote:
> On Jenkins 1.x we can call scriptlet entries using GET.
> On Jenkin 2.x, any GET attempts are being returned with an error that they
> must be done via POST
>
That's a security fix. See
https://www.jenkins.io/security/advisory/2017-04-
On Jenkins 1.x we can call scriptlet entries using GET.
On Jenkin 2.x, any GET attempts are being returned with an error that they
must be done via POST
I'm not finding anything in JIRA, but my search could be bad.
Has this functionality changed?
Thank you !
-
>From the documentation: h
