Closed mrx23dot closed 3 years ago
@mrx23dot Both issues #47 and #48 should now be fixed. I will publish a new version of the libary in the next few days, since I have to fix another issue before publishing a new version of the package.
I will test the changes, seems to be t he best parsing lib so far, thank you!
@mrx23dot The fixes are now included in the new release V2.0.5.
Found a few rare cases, parsing these zipped fillings gave "namespace couldn't be found" errors. It worked great on 2000 other symbols.
See SEC response to this at the end. They seem to suggest that the lib doesn't follow 301 perm.redirection, but I don't think that's the case because code says: _session.get(url, headers=headers, allow_redirects=True) Or the response is in a special html header. (location)
SEC's respons:
We assume you are aware that the namespace-uri is not the URL, but rather, that the namesace-uri designates a location (URL). So, we suspect that your software is trying to retrieve the taxonomy file http://xbrl.sec.gov/stpr/2018/stpr-2018-01-31.xsd. Please note that URL will return a 301 response header:
HTTP/1.1 301 Moved Permanently Date: Mon, 19 Jul 2021 19:52:38 GMT Server: AkamaiGHost Location: https://xbrl.sec.gov/stpr/2018/stpr-2018-01-31.xsd Connection: Keep-Alive Content-Length: 0
Not all software products will interpret this response correctly (although we haven't seen this particular problem in a couple of years).