Skip to content
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 bug #25215: max_input_time timeout misreported #1010

Closed
wants to merge 2 commits into from

Conversation

mj
Copy link
Member

@mj mj commented Jan 19, 2015

With this change PHP uses a different error message upon running into a timeout when it relates to max_input_type instead of max_execution_time.

I'm having a hard time coming with a test case for this, unfortunately.

With this change PHP uses a different error message upon running
into a timeout when it relates to max_input_type instead of
max_execution_time.
@@ -208,6 +211,7 @@ struct _zend_executor_globals {

/* timeout support */
zend_long timeout_seconds;
int timeout_type;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd prefer using an unsigned char here. More appropriate storage size

@jpauli jpauli added the Bug label Jan 20, 2015
@mj
Copy link
Member Author

mj commented Jan 22, 2015

@jpauli, thanks for your feedback. I've changed the variable type.

@smalyshev smalyshev added Feature and removed Bug labels Feb 1, 2015
@krakjoe
Copy link
Member

krakjoe commented Jan 5, 2017

@mj can you please rebase this to fix merge conflicts ?

(on a side note, use zend_uchar instead of unsigned char for portability)

I'm not sure why this wasn't merged, looks like a nice improvement that can go in master when it's fixed.

@krakjoe
Copy link
Member

krakjoe commented Jan 8, 2017

Unbelievably this was requested more than 10 years ago (2003): https://bugs.php.net/bug.php?id=25215

@krakjoe
Copy link
Member

krakjoe commented Feb 22, 2017

Having waited more than a month for feedback, and having received nothing, I'm closing this PR as it would appear abandoned.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants