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

Robust links alignment #115

Merged
merged 7 commits into from Aug 7, 2018

Conversation

Projects
None yet
2 participants
@shawnmjones
Collaborator

shawnmjones commented Aug 7, 2018

This consists of work for #114. I am leaving #114 open a while for further discussion, if necessary.

@shawnmjones shawnmjones self-assigned this Aug 7, 2018

@shawnmjones shawnmjones merged commit 0e8f812 into master Aug 7, 2018

1 check passed

continuous-integration/travis-ci/pr The Travis CI build passed
Details
@@ -122,7 +122,7 @@ On success, the social card service produces an HTTP 200 status response contain
</p>
</div>
</blockquote>
<script async src="http://mementoembed.ws-dl.cs.odu.edu/static/js/mementoembed.js" charset="utf-8"></script>
<script async src="http://mementoembed.ws-dl.cs.odu.edu/static/js/mementoembed-v20180806.js" charset="utf-8"></script>

This comment has been minimized.

@ibnesayeed

ibnesayeed Aug 7, 2018

Member

@shawnmjones if you are using version number in the file name just to avoid any browser caches, then you can use the number as query parameter instead of the file name (i.e., mementoembed.js?v=20180806 instead of mementoembed-v20180806.js). This way, the server will ignore any query parameters when serving a static file and serve whatever version of the file is present with that name, but the browser would be fooled to burst the cache. The reason of this change suggestion is because if you are tracking that file and not generating as the build process then renaming the file on every release would be messy.

@ibnesayeed

ibnesayeed Aug 7, 2018

Member

@shawnmjones if you are using version number in the file name just to avoid any browser caches, then you can use the number as query parameter instead of the file name (i.e., mementoembed.js?v=20180806 instead of mementoembed-v20180806.js). This way, the server will ignore any query parameters when serving a static file and serve whatever version of the file is present with that name, but the browser would be fooled to burst the cache. The reason of this change suggestion is because if you are tracking that file and not generating as the build process then renaming the file on every release would be messy.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment