Skip to content

Fingerprinting SVGs #1741

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

Merged
merged 1 commit into from
May 8, 2019
Merged

Fingerprinting SVGs #1741

merged 1 commit into from
May 8, 2019

Conversation

markcatley
Copy link
Contributor

In the production build all the SVGs are copied into dist/assets without fingerprints. All other assets have fingerprints. Since all files in dist/assets are served with far-future cache headers there would be cache issues if the files were ever updated. This is not major issue as these files are not used in normal operations.

Closes #1575

In the production build all the SVGs are copied into dist/assets without fingerprints. All other assets have fingerprints. Since all files in dist/assets are served with far-future cache headers there would be cache issues if the files were ever updated. This is not major issue as these files are not used in normal operations.

Closes rust-lang#1575
@markcatley
Copy link
Contributor Author

I checked this by inspecting the dist/assets folder and then ensured the homepage rendered properly using npx ember serve --env production --proxy https://crates.io.

@jtgeibel
Copy link
Member

jtgeibel commented May 8, 2019

Thanks for tracking this down @markcatley.

@bors r+

@bors
Copy link
Contributor

bors commented May 8, 2019

📌 Commit c6d1853 has been approved by jtgeibel

@bors
Copy link
Contributor

bors commented May 8, 2019

⌛ Testing commit c6d1853 with merge ba79f83...

bors added a commit that referenced this pull request May 8, 2019
Fingerprinting SVGs

In the production build all the SVGs are copied into dist/assets without fingerprints. All other assets have fingerprints. Since all files in dist/assets are served with far-future cache headers there would be cache issues if the files were ever updated. This is not major issue as these files are not used in normal operations.

Closes #1575
@bors
Copy link
Contributor

bors commented May 8, 2019

☀️ Test successful - checks-travis
Approved by: jtgeibel
Pushing ba79f83 to master...

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

Successfully merging this pull request may close these issues.

Hashify filenames for all ember assets under /dist/assets
3 participants