Port down to AEM 6.5.x #40
Merged
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
… and Location header, but HTTP 200 and do manual continuation call. Also avoid strange freeze of browser in AEM 6.5.7 on $.ajax
Closed
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.
That solves most of #31 .
Mostly layout fixes were needed. There was a seriously weird problem that the tab blocked in Chrome at 100% on every content request in AEM 6.5.x (I assume in JQuery) - I tracked that down to the content creation request being HTTP 202 with a Location header and changed that mechanism to return the stream ID for the continuation in a JSON response.
It still works only with Java 11, though, since we use the asynchronous featores of java.net.http and the HttpClient 4 available on AEM 6.5.x does not have asynchronous features.