Currently files are deployed on blob storage directly, making a default Angular website generated by ng CLI available, but with some limitations:
Redirection to index.html file is working through a workaround: 404 errors redirects to root document, but ideally this should be done using some URL rewriting rules
HTTPS cannot be enforced
HTTPS cannot be used with custom domains
No automatic compression support
All these points could be addressed by configuring Azure CDN on top of the static website.
Though as this incurs additional charges for the deployed website, maybe we would like to make this extra layer optional, prompting the user during initial setup?
Type of change
Please delete options that are not relevant.
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
Description
Currently files are deployed on blob storage directly, making a default Angular website generated by ng CLI available, but with some limitations:
index.htmlfile is working through a workaround: 404 errors redirects to root document, but ideally this should be done using some URL rewriting rulesAll these points could be addressed by configuring Azure CDN on top of the static website. Though as this incurs additional charges for the deployed website, maybe we would like to make this extra layer optional, prompting the user during initial setup?
Type of change
Please delete options that are not relevant.