We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
No description provided.
The text was updated successfully, but these errors were encountered:
Angela Bartz commented: We already have a ProxyPass that redirects Sparkling Water 2.2, 2.1, and 2.0 Scaladocs to /latest-stable. For example:
ProxyPass "/sparkling-water/2.2/latest-stable/" "http://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.2/7/"
Ideally, the HTML output should point to a similar location/path so that there is no need for another ProxyPass statement.
https://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.0/22/userguide/index.html#package https://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.1/21/userguide/index.html#package https://h2o-release.s3.amazonaws.com/sparkling-water/rel-2.2/7/userguide/index.html#package
Sorry, something went wrong.
JIRA Issue Migration Info
Jira Issue: SW-703 Assignee: Jakub Hava Reporter: Jakub Hava State: Resolved Fix Version: 2.0.23 Attachments: N/A Development PRs: Available
Linked PRs from JIRA
#560
JIRA Issue Migration Info Cont'd
Jira Issue Created Date: 2018-02-02T02:35:44.912-0800
jakubhava
No branches or pull requests
No description provided.
The text was updated successfully, but these errors were encountered: