Use deep links to Herd-UI pages about herd-mdl HOT 8 CLOSED

1. Research the above solutions

from herd-mdl.

You can mark this as closed when the the first solution is implemented in the CFT for when cloudfront is not used with only an s3 static web page configuration.

The solution is to simply set the Error Page for s3 static web page to index.html

The solution for cloudfront is already implemented inside the CFT for Cloudfront which was to set a custom error response for 404's as index.html/200.

from herd-mdl.

@kenisteward But we don't want to show them error. we will redirect them to the page where they come from. Like if they are trying to access baseUrl/data-entities/nsx/xxx they need to be go to that page as well. Will configuring 404's as index.html/200 will redirect to data-entities/nsx/xxx if they came from that page?

from herd-mdl.

@aniruddhadas9 the error won't be shown with the config i gave.

from herd-mdl.

from herd-mdl.

We have this story in the current sprint. We need to test with both Auth and No-Auth scenarios, as we use Cloudfront and S3 bucket implementations respectively. @rongwang0930 found that we need to make a change for No-Auth case (index.html for S3). We have not tested this with Cloudfront yet. So, we will continue this when we start the story. Thanks @kenisteward and @aniruddhadas9 for looking into this.

from herd-mdl.

@nateiam the smoke tests that are coupled with the app actually will tell you if this fails or not. they just need to be configured to run.

from herd-mdl.

Verified in no-auth
In Auth, the deep links work -- but it will prompt you for auth anytime you reload or use a deep link

from herd-mdl.