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
Update links to Spring Security's reference documentation #28618
Comments
Is it live yet? I get a 404 currently. |
As discussed previously, it'd also be good to have a versioned URL so that someone reading a certain version of Boot's docs is linked to the matching version of Security's docs. |
Sorry it I pointed to the incorrect URL. It should be http://docs.spring.io/spring-security/reference/
The URL for a specific version is For example, http://docs.spring.io/spring-security/reference/5.6.0-RC1 is the link for 5.6.0-RC1. For now 5.6.0-RC1 is the latest release (there are no GA releases either), so it redirects to the versionless URL. The URL will stop redirecting once there is a newer version available. Similarly, http://docs.spring.io/spring-security/reference/5.6 will always point to the latest 5.6.x release. For now it redirects to the versionless URL, but once there is a newer GA version available 5.6 will stop redirecting to the versionless URL and point to the latest patch release. This logic is very similar to the symlinks we currently use, but uses redirects instead. |
Thanks, Rob. We currently take the actual Security version and then remove the last spring-boot/spring-boot-project/spring-boot-docs/build.gradle Lines 259 to 260 in 313470a
I think that'll continue to work although I wonder if it's exactly what we want. https://docs.spring.io/spring-security/reference/5.6.0-SNAPSHOT and https://docs.spring.io/spring-security/reference/5.6.1-SNAPSHOT are not found so it looks like we have to do something for |
The docs group has made some changes to how the URLs are going to be handled. Spring Boot should update spring-security attribute to point to https://spring.io/projects/spring-security/reference
The text was updated successfully, but these errors were encountered: