ngOnInit not firing when clicking browser's back button.

I’m submitting a…

[ ] Regression (a behavior that used to work and stopped working in a new release)
[x] Bug report  
[ ] Performance issue
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:

Current behavior

I’m having problems with routes that involve parameters. When I try to go back with the browser’s back button from a route with a parameter like person/:id the ngOnInit of the previous component doesn’t fire. This only happens when deploying the app to production.

Expected behavior

The ngOnInit of the previous component should be called and render the component correctly.

Minimal reproduction of the problem with instructions

Steps to reproduce the error with the angular’s tutorial:

• Download the tutorial from Angular’s tutorial and run npm install
• Build the app with the command ng build --prod --build-optimizer or ng build --prod
• Upload the static files generated by the previous step to an nginx or apache server with the respective configuration file having the recomended lines of code in angular docs. Angular Deployment
• Click one of the top heros in the dashboard.
• Click browser’s back button.

By following those steps you will see the top heros are not loaded in the dashboard which is exactly the same problem I’m having with my app. This is be cause ngOnInit is not called when going back specifically with the back button.

Environment

Angular version: 6.0.0 and 7.0.1

Browser:
- [x] Chrome (desktop) version 69.0
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [x] Firefox version 63.0
- [x] Safari (desktop) version 12
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: 10.5.0
- Platform:  Mac, Linux, Windows

Others:
This problem doesn't accurs while using development mode ng serve and trying the app locally.
It only happens when deploying to a subdomain like "subdomain.domain.com" but works perfectly in a normal domain "domain.com". I'm not sure if this could be considered a normal behavior.