Embed XSL into results XML file to overcome same origin policy problems #5
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
…problems when the file is accessed locally
OndraM
force-pushed
the
master
branch
2 times, most recently
from
3e1714c
to
a483899
Compare
OndraM
added a commit
that referenced
this pull request
May 13, 2015
Embed XSL into results XML file to overcome same origin policy problems
|
Tested on local project, looks good to merge. |
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.
When the results.xml is accessed locally, same-origin policy didn't allow to load the XSLT from other files. Same problem occurs with http address.
Probably the only solution is to embed the XSL stylesheet right into the XML file.
cc @tenerd @dudla @mplmc