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
When zpm deploy uploads an index.html page, it incorrectly assumes that the Swift installation is running the staticweb middleware and that this is configured to serve index.html as the default file.
This assumption is not universally correct and it would be better if it printed the full URL instead.
The text was updated successfully, but these errors were encountered:
Before, we would show the user that we had deployed into
server/v1/account/container/path/
This relied on the staticweb middleware being installed and a suitable
web index being configured. We now show
server/v1/account/container/path/index.html
instead when an index.html file is being deployed. If no index.html
file is uploaded (zapps with a non-standard UI), we show the same URL
as before and the users will have to sort things out by themselves.
Before, we would show the user that we had deployed into
server/v1/account/container/path/
This relied on the staticweb middleware being installed and a suitable
web index being configured. We now show
server/v1/account/container/path/index.html
instead when an index.html file is being deployed. If no index.html
file is uploaded (zapps with a non-standard UI), we show the same URL
as before and the users will have to sort things out by themselves.
When
zpm deploy
uploads anindex.html
page, it incorrectly assumes that the Swift installation is running the staticweb middleware and that this is configured to serveindex.html
as the default file.This assumption is not universally correct and it would be better if it printed the full URL instead.
The text was updated successfully, but these errors were encountered: