[
https://issues.apache.org/jira/browse/SHINDIG-1356?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12876579#action_12876579
]
Bastian Hofmann commented on SHINDIG-1356:
------------------------------------------
we ran into this issue on our platform. it's possibly very specific to our
setup, but the patch should cause no problems for any other setup as well.
i can't really tell you any more about it, since this issue was fixed in our
local implementation about one year ago by some colleague. in preparation for
our migration to the current version of shindig and opensocial 0.9 i'm revising
all patches and feature additions we did over the last year and will be looking
at which are worth comitting. so you can expect some more small issues in the
next weeks ;)
> Remove leading characters in XHR callback processing which may be inserted if
> apache has transfer-encoding: chunked
> -------------------------------------------------------------------------------------------------------------------
>
> Key: SHINDIG-1356
> URL: https://issues.apache.org/jira/browse/SHINDIG-1356
> Project: Shindig
> Issue Type: Bug
> Components: Javascript
> Reporter: Bastian Hofmann
> Priority: Minor
>
> When running on Apache with transfer-encoding: chunked there may be some line
> breaks \n before the message. The following fix filters these out:
> Index: features/src/main/javascript/features/core.io/io.js
> ===================================================================
> --- features/src/main/javascript/features/core.io/io.js (Revision 952257)
> +++ features/src/main/javascript/features/core.io/io.js (Arbeitskopie)
> @@ -132,6 +132,9 @@
> return;
> }
> var txt = xobj.responseText;
> + // remove any leading characters like \n
> + // this happens if apache has transfer-encoding: chunked
> + txt = txt.substr(txt.indexOf(UNPARSEABLE_CRUFT))
> // remove unparseable cruft used to prevent cross-site script inclusion
> txt = txt.substr(UNPARSEABLE_CRUFT.length);
> // We are using eval directly here because the outer response comes from
> a
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
