Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Restore HTTP access to liquibase schemas
See original GitHub issueHi folks,
the error re-appeared again. Today, the call curl -v http://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.9.xsd delivers 301 moved permanently (Location: https://www.liquibase.org/xml/ns/dbchangelog/dbchangelog-3.9.xsd).
SAX Parsers in Keycloak for example are not able to get them. Could you please re-enable the unsafe http access?
Thanks,
Simon
_Originally posted by @zambrovski in https://github.com/liquibase/liquibase/issues/1153#issuecomment-1026597782_
Issue Analytics
- State:
- Created 2 years ago
- Reactions:3
- Comments:8 (2 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Hi @zambrovski, @leitus and @AleksanderGrzybowski @lbanas This should be fixed now.
Yes, that may be a pretty old version, it is
version 3.8.9 #73 built at Mon Apr 06 09:32:58 UTC 2020. Edit: I know I can update the URL with HTTPS and it will work (someone responded in the other ticket), but it would be cool if it kept working as it is. Our setup doesn’t allow to change changelog files without rebuilding dozens of Docker images, though, we’ll do it if necessary. Thanks a lot!