Replace expired msdn link with latest web archive copy #9050
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
spring-projects-issues
added
the
status: waiting-for-triage
|
If I understand the build log correctly build failed because 1 of integration tests failed: I don't think changes in the PR could cause it. Please rerun build if possible |
|
Thanks, @muRn, for the PR! In preparation for merging, will you please squash your commits? |
Initial link expired in March, 2016. Latest copy found in web archive is from February, 2016
|
Squashed my commits & force pushed. Is it OK now? |
|
Thanks, @muRn, for the PR! It's now merged into |
jzheaux
added
in: web
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Javadoc for
org.springframework.security.config.annotation.web.configurers.HeadersConfigurerclass contained MSDN blog link that expired in March, 2016 and is not usable since. I decided to replace it with latest possible web archive copy of that blog post (from February, 2016). I didn't create issue for such a minor change, hope it's OK.