Skip to content

Violation of content security policy directive "default-src 'self' #103

@avenethermale

Description

@avenethermale

Hello!
First of all, THANK YOU for coming up with this plugin!

I use the plugin to send information to my slack channel, and in the slack channels, I set the notification setting to 'Mentions' so I would only get notified when the 'My keywords' I registered in slack are included in the message sent via the plugin.

So let's say if I registered my name to be 'My keywords' only when redmine issues with my name in it(as assignee, requested, in description, etc) is created/updated, i would get slack notification.

I was using it just fine and out of no where a few weeks ago, this function just stopped work.

I checked out slack's notifications-consol log, and it says slack is not able to notify me "because it violates the following Content Security Policy directive: "default-src 'self' https://app.slack.com/ app://*". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback."

here is the full log message:
}
[09/23/22, 11:11:44:934] error: Refused to connect to 'https://slack.com/apps/sentryproxy/api/5277886/envelope/?sentry_key=fd30fe469dbf4aec9db40548e5acf91e&sentry_version=7' because it violates the following Content Security Policy directive: "default-src 'self' https://app.slack.com/ app://*". Note that 'connect-src' was not explicitly set, so 'default-src' is used as a fallback.

[09/23/22, 11:11:45:072] info: Store: PREPARE_AND_REVEAL_LOGS
[09/23/22, 11:11:45:072] info: Store: CLOSE_APP_MENU
[09/23/22, 11:11:45:095] info: Store: UPSERT_WEB_CONTENTS {
"id": 7,
"state": "unloaded"

Do you know why slack is suddenly refusing the message? is there fix to this?? HELPP!!!

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions