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
Yarn documents that the following is a stub and should not be directly included: "@types/commander": "2.12.2",
Changing to Spring Boot 3 results in the redirects going away (but the lack of redirect support in fw-cli still exists even if mod-workflow is not using redirects for / ending paths).
The text was updated successfully, but these errors were encountered:
kaladay
changed the title
Fix "HTTP/1.1 301 Moved Permanently" failures.
Fix "HTTP/1.1 301 Moved Permanently" failures and replaced deprecated modules.
Feb 1, 2024
In our local environment, valid "HTTP/1.1 301 Moved Permanently" responses are returned.
These are being treated as errors.
As an example, a request to
http://localhost:9001/workflow/triggers
might get redirected tohttp://localhost:9001/workflow/triggers/
.This needs to be supported.
Either add a way to automatically append a
/
or properly handle the permanent (or temporary) redirect.The uuid module needs to be upgraded to at least a
7.0.0
version and must be manually added as a direct dependency.This seems to have worked but there are problems when talking to mod-workflow:
Yarn documents that the following is a stub and should not be directly included:
"@types/commander": "2.12.2",
Changing to Spring Boot 3 results in the redirects going away (but the lack of redirect support in fw-cli still exists even if mod-workflow is not using redirects for
/
ending paths).The text was updated successfully, but these errors were encountered: