Skip to content
New issue

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

Rewrite Whitehall asset URLs in Content Store content #322

Open
chrisroos opened this issue Dec 5, 2017 · 1 comment
Open

Rewrite Whitehall asset URLs in Content Store content #322

chrisroos opened this issue Dec 5, 2017 · 1 comment

Comments

@chrisroos
Copy link
Contributor

Whitehall's non-attachment assets can be accessed via both www.gov.uk/government/uploads/... and assets.publishing.service.gov.uk/government/uploads/.... We're in the process of changing this so that they're only accessible via assets.publishing.service.gov.uk.

Some asset URLs using www.gov.uk are written into content in the Content Store. We'll want to rewrite these so that they use assets.publishing.service.gov.uk instead.

For example, this Heathrow expansion consultation content contains a link to a consultation response form asset at https://www.gov.uk/government/uploads/system/uploads/consultation_response_form_data/file/622/revised-draft-airports-nps-response-form.docx (under the details > ways_to_respond > attachment_url key). We'll want to update these so that they're using assets.publishing.service.gov.uk instead.

@chrisroos chrisroos changed the title Rewrite Whitehall asset URLs in content stored in Content Store Rewrite Whitehall asset URLs in Content Store content Dec 5, 2017
@chrisroos
Copy link
Contributor Author

We updated Whitehall to write assets.publishing.service.gov.uk (instead of www.gov.uk) to the Content Store in alphagov/whitehall#3634.

We added a redirect from www.gov.uk to assets.publishing.service.gov.uk in alphagov/whitehall#3627.

I'm not yet sure what to do about the more general issue of Content Store content that contains links to assets using www.gov.uk.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants