-
Notifications
You must be signed in to change notification settings - Fork 1.9k
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
fix some errors on error_exception.php #308
Conversation
… value Signed-off-by: Mutasim Ridlo, S.Kom <[email protected]>
Signed-off-by: Mutasim Ridlo, S.Kom <[email protected]>
Signed-off-by: Mutasim Ridlo, S.Kom <[email protected]>
hope to fix this bug soon!! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changing the $request to $response makes sense. That was my typo.
However, I unsure what the bug is in lines 283-286 that you're replacing. It shouldn't be an array because it's calling the getHeaderLine()
which combines them into a single string value.
Yes, you're correct. But, $headers will contain array if we do a POST request.
I see you do a same thing in this commit, file toolbar.tpl.php lines 191-200. But, it's up to you, I will revert back some changes in lines 283-286 to previous state if you wish. |
Good point. I was likely being lazy on that last fix. :) I need to go back through the HTTP spec because it doesn't make sense to me that should work - having 2 headers by the same name. I'm just afraid it's a deeper problem than the toolbar, so will investigate. |
Alright, just checked the HTTP Message spec and the spec does allow for multiple headers with the same field-name, so it looks like we're good to merge this. Thanks! Though it does seem weird that we're getting 2 identical headers on a post request... |
You're welcome :-) |
fix some errors related to request & response on error_exception.php