| Summary: | Invalid Error 413 crash Apache | ||
|---|---|---|---|
| Product: | Apache httpd-2 | Reporter: | Ricardo <ricardo.nuno.rodrigues> |
| Component: | Core | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
| Status: | RESOLVED LATER | ||
| Severity: | normal | CC: | ricardo.nuno.rodrigues |
| Priority: | P2 | Keywords: | MassUpdate |
| Version: | 2.2.17 | ||
| Target Milestone: | --- | ||
| Hardware: | PC | ||
| OS: | All | ||
|
Description
Ricardo
2010-12-10 15:02:22 UTC
need some sign this isn't just PHP crashing in your errordocument. Hi Eric, Please rephrase because I don't understand your point. The PHP code run is the same on both cases, is this the question? (In reply to comment #2) > Hi Eric, > Please rephrase because I don't understand your point. > > The PHP code run is the same on both cases, is this the question? It's no easy task to analyze a windows dump and tell what component crashed, much less why. But generally when Apache crashes while serving a PHP resource, the PHP interpreter is the culprit until shown otherwise. Eric, The problem is this: Works: ErrorDocument 413 http://localhost/v1/index.php/candidate/my_profile/photo/size_error/pt Crashes: ErrorDocument 413 /v1/index.php/candidate/my_profile/photo/size_error/pt PHP code is the same. The diference is the Apache isn't understanding the routing. What is the correct syntax for this case? I didn't found documentation. I can have http://www.AAA.com/v1/index.php/candidate/my_profile/photo/size_error/pt and http://www.BBB.com/v1/index.php/candidate/my_profile/photo/size_error/pt What's the correct ErrorDoucument definition? Thanks Ricardo How do you know your crash is related to apache "not understanding the routing" and not PHP crashing when called for an internal redirect / local error document? I suggest you debug the configuration without a PHP script generating the response and discuss on the user support mailing list. Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated. |