# Obtendo erro de rota do Rails em vez de 404
**URL:** https://meta.discourse.org/t/getting-rails-route-error-instead-of-404/103754
**Category:** Development
**Created:** [Dezembro 8, 2018, 10:19am UTC](https://meta.discourse.org/t/getting-rails-route-error-instead-of-404/103754 "2018-12-08T10:19:06Z")
**Posts on this page:** 3
**Page:** 1
### Author:  [@kleinfreund](https://meta.discourse.org/u/kleinfreund)
#### Post date: [Dezembro 8, 2018, 10:19am UTC](https://meta.discourse.org/t/getting-rails-route-error-instead-of-404/103754/1 "2018-12-08T10:19:06Z")
Starting Discourse in development mode and opening [http://localhost:3000/x](http://localhost:3000/x) doesn’t produce a 404 page like [https://meta.discourse.org/x](https://meta.discourse.org/x) does. Instead, I get the Rails routing error page:
```plaintext
No route matches [GET] "/x"
```
> **Full stack trace**
>
> ```plaintext
> actionpack (5.2.0) lib/action_dispatch/middleware/debug_exceptions.rb:65:in `call'
> actionpack (5.2.0) lib/action_dispatch/middleware/show_exceptions.rb:33:in `call'
> logster (1.2.11) lib/logster/middleware/reporter.rb:31:in `call'
> railties (5.2.0) lib/rails/rack/logger.rb:38:in `call_app'
> railties (5.2.0) lib/rails/rack/logger.rb:28:in `call'
> config/initializers/100-quiet_logger.rb:16:in `call'
> config/initializers/100-silence_logger.rb:29:in `call'
> actionpack (5.2.0) lib/action_dispatch/middleware/remote_ip.rb:81:in `call'
> actionpack (5.2.0) lib/action_dispatch/middleware/request_id.rb:27:in `call'
> rack (2.0.5) lib/rack/method_override.rb:22:in `call'
> actionpack (5.2.0) lib/action_dispatch/middleware/executor.rb:14:in `call'
> actionpack (5.2.0) lib/action_dispatch/middleware/static.rb:127:in `call'
> rack (2.0.5) lib/rack/sendfile.rb:111:in `call'
> lib/middleware/missing_avatars.rb:21:in `call'
> lib/middleware/turbo_dev.rb:34:in `call'
> rack-mini-profiler (1.0.0) lib/mini_profiler/profiler.rb:285:in `call'
> message_bus (2.1.6) lib/message_bus/rack/middleware.rb:63:in `call'
> railties (5.2.0) lib/rails/engine.rb:524:in `call'
> railties (5.2.0) lib/rails/railtie.rb:190:in `public_send'
> railties (5.2.0) lib/rails/railtie.rb:190:in `method_missing'
> rack (2.0.5) lib/rack/urlmap.rb:68:in `block in call'
> rack (2.0.5) lib/rack/urlmap.rb:53:in `each'
> rack (2.0.5) lib/rack/urlmap.rb:53:in `call'
> puma (3.11.4) lib/puma/configuration.rb:225:in `call'
> puma (3.11.4) lib/puma/server.rb:632:in `handle_request'
> puma (3.11.4) lib/puma/server.rb:446:in `process_client'
> puma (3.11.4) lib/puma/server.rb:306:in `block in run'
> puma (3.11.4) lib/puma/thread_pool.rb:120:in `block in spawn_thread'
>
> ```
I disabled the plugin I’m developing, but that doesn’t affect this problem.
Note that a link with `href="/x"` does produce the expected 404 error page, only a regular request doesn’t.
I’m not sure how to categorize this as I’m certain this must be an issue on my end, not a bug with Discourse.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [Dezembro 8, 2018, 2:45pm UTC](https://meta.discourse.org/t/getting-rails-route-error-instead-of-404/103754/2 "2018-12-08T14:45:23Z")
I think that’s just how development mode works.
---
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [Dezembro 8, 2018, 9:33pm UTC](https://meta.discourse.org/t/getting-rails-route-error-instead-of-404/103754/3 "2018-12-08T21:33:19Z")
Yeah, that’s a Rails feature when used in development mode.