Skip to content
This repository was archived by the owner on Nov 22, 2024. It is now read-only.

Return a 404 or 500 status code #969

Closed
tislars opened this issue Apr 25, 2018 · 3 comments
Closed

Return a 404 or 500 status code #969

tislars opened this issue Apr 25, 2018 · 3 comments

Comments

@tislars
Copy link

tislars commented Apr 25, 2018

  • I'm submitting a ...
- [ ] bug report
- [x] feature request
  • What modules are related to this Issue?
- [ ] aspnetcore-engine
- [ ] common
- [x] express-engine
- [ ] hapi-engine
- [ ] module-map-ngfactory-loader
  • Do you want to request a feature or report a bug?
    Feature

  • What is the current behavior?
    When the user ends up on a non-existing page, the browser returns a 200 http status code.

  • What is the expected behavior?
    I'd would like to be able to return a 404 or 500 status code.

  • What is the motivation / use case for changing the behavior?
    For SEO it is important to return correct status codes.

  • Please tell us about your environment:

 - Angular version: 4
 - Browser: all
 - Language: Typscript
 - OS:  Mac OS X
 - Platform: NodeJS
  • Other information
    I followed this solution from a previous reported issue. However, my server.ts differs from theirs, as mine is the same as the official repository' one.
@Toxicable
Copy link

duplicate of angular/angular#55281

@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants