Saw '301 Moved Permanently' when parsing XML changelog

Hi, just now I got this error when I restarting my Spring Boot App.

and this is line 2 in the changelog

<databaseChangeLog xmlns="" xmlns:ext="" xmlns:pro="" xmlns:xsi="" xsi:schemaLocation="">

I got this xml when I generate a diff from two database. For a quick fix, I changed 4.1 to 3.9 since I need the app to be running right now.
Can you let me know how to fix this issue properly?
Thank you


We have the same error since few hour. We update to 4.6.2 (latest) and the problem disapear.
On maven repo, this version doesn’t have the CVE-2021-23463 vulnérability…

On 4.6.2, the spring configuration work’s and the liquibase::diff goal work to !

I don’t know what is the difference on the online xsd and how this latest version get this xsd online… i hope that is a misconfiguration and not to force to migrate to the latest version… No communication on the website about this.

Sorry for the problems.

The is is that a “require https” setting somehow got enabled for those XSD urls. We’re shifting our website hosting provider and despite the fact that we explicitly tested for this requirement on staging, something seems different in their new production settings. We’re actively working with them to resolve the problem.

In general, Liquibase should read the xsd files bundled in the jar rather than try to download them but there have been a few versions over the years which had a bug that caused them to pull them from the network.

Upgrading to the current 4.6.2 version will address it from whatever versions have the “download the xsd” bug. Switching the XSD URL in your file to https instead of http will work too. Otherwise, we should hopefully have the redirecting issue fixed on our our side soon.


The server config should be fixed up now. Let us know if you’re still seeing problems.


It looks like there’s a separate issue with it blocking user-agent=java requests now too…

The fun of infrastructure changes. We’re working on getting it resolved.


The user-agent block has been resolved now as well, so everything should be fixed up now.

Let me know if you still have issues.


1 Like

Hi Nathan,
I just checked and it works perfectly now. Thank you