Christian Bewernitz

Thx for the link, but that is not what I'm looking for. I'm looking for reporting headers made by the browser or anything that I'm not in control of, which...

Thx for the report, I'm currently not able to invest enough time into this project. The description sounds very reasonable, so if someone is able to provide a PR with...

Sorry for the delay in processing this. I still have one very busy week in front of me, but afterwards I should be able to find the time for this...

Hey @hungarian-notation I finally managed to look into it closer and still have some doubts: I'm still having a hard time wrapping my head around the topic, but I know...

Thank you for filing the feature request. I need to check what the current behavior is, but I assume it serializes the element representation to its XML string? If that...

xmldom in its current state is an inconplete ponyfill, indicated by the version number 0.* And there is currently no differentiation of different element types at all. So the maximum...

Thx for the report, the issue is that there is no URI defined for the namespace used. For all namespaces that are not defined in the document, you have to...

Not sure if it is the same issue as the one reported originally, since the namespace was not included in the original posted example. I will have a look at...

> Parsing the sample message will raise namespace error in libxml2/nokogiri. @ahacker1-securesaml I'm not sure why the behavior of that library should be relevant. The browser is able to parse...

@cjbarth I think I need more information to be able to reproduce the issue. I see that there is some discussion going on in https://github.com/node-saml/xml-crypto/pull/501 and you made plenty of...