We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Slack's webhooks returned a 403, but the put step was not marked as a failure.
> Host: hooks.slack.com > user-agent: curl/7.69.1 > accept: */* > content-length: 170 > } [5 bytes data] * We are completely uploaded and fine { [5 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [230 bytes data] * TLSv1.3 (IN), TLS handshake, Newsession Ticket (4): { [230 bytes data] * old SSL session ID is stale, removing { [5 bytes data] * Connection state changed (MAX_CONCURRENT_STREAMS == 100)! } [5 bytes data] < HTTP/2 403 < date: Thu, 22 Jun 2023 20:03:08 GMT < server: Apache < vary: Accept-Encoding < strict-transport-security: max-age=31536000; includeSubDomains; preload < x-slack-unique-id: ZJSo_MkmMKScUpMEbqMjkwAAAA4 < x-slack-backend: r < referrer-policy: no-referrer < access-control-allow-origin: * < x-frame-options: SAMEORIGIN < content-type: text/html < content-length: 13 < via: 1.1 slack-prod.tinyspeck.com, envoy-www-iad-bvwfaqof, envoy-edge-iad-brfptmiy < x-envoy-upstream-service-time: 5 < x-backend: main_normal main_canary_with_overflow main_control_with_overflow < x-server: slack-www-hhvm-main-iad-tfic < x-slack-shared-secret-outcome: no-match < x-edge-backend: envoy-www < x-slack-edge-shared-secret-outcome: no-match < { [13 bytes data] 100 183 100 13 100 170 590 7727 --:--:-- --:--:-- --:--:-- 8318 * Connection #0 to host hooks.slack.com left intact invalid_token
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Slack's webhooks returned a 403, but the put step was not marked as a failure.
The text was updated successfully, but these errors were encountered: