Update reference to klick2contact.com #213
Conversation
Smokey has started failing on `cucumber -p staging_aws features/finder_frontend.feature:90 # Scenario Outline: Check search results and analytics` This is the error: ``` Refused to connect to 'https://hmpowebchat.klick2contact.com/v03/providers/HMPO/api/availability.php' because it violates the following Content Security Policy directive: "connect-src 'self' *.publishing.service.gov.uk *.staging.publishing.service.gov.uk www.gov.uk *.dev.gov.uk www.google-analytics.com ssl.google-analytics.com stats.g.doubleclick.net www.googletagmanager.com www.tax.service.gov.uk hmrc-uk.digital.nuance.com gov.klick2contact.com www.signin.service.gov.uk lux.speedcurve.com". ``` The content security policy originally included `gov.klick2contact.com` in 7c1670b in January 2020. However, we started referencing `hmpowebchat.klick2contact.com` in 1a5adccfd19435c3bceaeab402224775ecbae638 in March 2020. I'm not sure why this has only started failing today, nor whether `gov.klick2contact.com` is still in use. My assumption is that that is a legacy thing and we should only allow connections to `hmpowebchat.klick2contact.com` from now on. If that assumption is wrong, it will be relatively simple to add `gov.klick2contact.com` back in.
There was a problem hiding this comment.
Thanks for fixing, I was able to reproduce this issue on https://www.gov.uk/government/organisations/hm-passport-office/contact/hm-passport-office-webchat.
|
Also, it looks like we discovered this problem by accident (this page happens to be the 11th result in search results for the query "passport" https://github.com/alphagov/smokey/blob/main/features/finder_frontend.feature#L90). Should we add a feature test that this page is working as expected? |
Good shout, Bill. I'll raise a follow-up PR. |
Smokey has started failing on
cucumber -p staging_aws features/finder_frontend.feature:90 # Scenario Outline: Check search results and analyticsThis is the error:
The content security policy originally included
gov.klick2contact.comin 7c1670b in January 2020.However, we started referencing
hmpowebchat.klick2contact.comin 1a5adccfd19435c3bceaeab402224775ecbae638 in March 2020.I'm not sure why this has only started failing today, nor whether
gov.klick2contact.comis still in use.My assumption is that that is a legacy thing and we should only allow connections to
hmpowebchat.klick2contact.comfrom now on.If that assumption is wrong, it will be relatively simple to add
gov.klick2contact.comback in.