Update best-bet behavior in ContentUrlTag.java #883
Closed
+5
−1
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
|
|
Thanks @jovelromeo, It's OK with me. Apart for non functional changes, we a tradition of creating Jira issues. Could you please create one? |
|
BTW, I did not notice that you fixed the 18.12 branch. I consider this more as a bug than an improvement. So I'll merge in trunk and backport in 18.12 and 24.09. |
|
This has been handled with https://issues.apache.org/jira/browse/OFBIZ-13217 |
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.
Explanation
If no.http is enable the best-bet behavior should probably be to use secure prefix.