-
-
Notifications
You must be signed in to change notification settings - Fork 246
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unhandled notice exception instead of 404 handling #190
Comments
Already fixed in 968d04f but not yet released |
Tested with 968d04f and it still not works.
public function trigger404($match = null)
if (isset($this->afterRoutes[$this->requestedMethod])) {
$this->trigger404($this->afterRoutes[$this->requestedMethod]);
} My suggestion is to revert/adjust 968d04f and just to remove transferred but unused argument to |
I’m open to a PR that would fix this. |
Sorry for the question but do you know when the fix will be available? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Notice: this issue is applicable for any HTTP method. Lets use PUT for example.
The Router throws 'Undefined index: PUT' PHP notice when there is attempt to call PUT method, and no PUT routers were registered.
Snipet to reproduce:
Expected: 404 handler triggered without PHP notices.
Actual: PHP notice
The text was updated successfully, but these errors were encountered: