You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can SweetXml be configured / motivated to not map single \r characters to \n? This causes issues when parsing XML form AWS S3 storage service when object names contain \r (which although not smart to use, is legal to use).
Working with this XML returned from Amazon AWS S3 storage service:
Note that the S3 Key's with \r in them have their \r characters mapped to \n. In general this is probably "right" and in conformance with the XML specs wrt end of line handling, but I think we should ideally be able to use SweetXml in some way against this type of input and have the \r and other similar characters mapped to their XML escape equivalents (e.g., in the \r case).
Can SweetXml be used in a way in which this mapping of \r to \n is not done?
The text was updated successfully, but these errors were encountered:
Can SweetXml be configured / motivated to not map single
\r
characters to\n
? This causes issues when parsing XML form AWS S3 storage service when object names contain\r
(which although not smart to use, is legal to use).Working with this XML returned from Amazon AWS S3 storage service:
I used the SweetXml xpath snippet from lib/ex_aws/s3/parsers.ex in the ex_aws/ex_aws_s3 project, as-is:
Note that the S3 Key's with
\r
in them have their\r
characters mapped to\n
. In general this is probably "right" and in conformance with the XML specs wrt end of line handling, but I think we should ideally be able to use SweetXml in some way against this type of input and have the\r
and other similar characters mapped to their XML escape equivalents (e.g.,
in the\r
case).Can SweetXml be used in a way in which this mapping of
\r
to\n
is not done?The text was updated successfully, but these errors were encountered: