[Bug 1065555] [NEW] Known segfault in 1.1.19 (the current stable)

[Launchpad Bug Tracker]

You have been subscribed to a public bug by Thomas Ward (trekcaptainusa-tw):

[IMPACT]

 * This bug has a severe impact on users running nginx.

 * This bug breaks the try_files directive, in that certain URIs and
configurations will cause segfaults.

[TESTCASE]

 * The nginx forums post at
http://forum.nginx.org/read.php?2,231787,231787#msg-231787 originally
posted by Tom Vaughan (tvaughan) has sample configurations and sample
tests.  Use of those methods should reproduce this bug.  This fix should
prevent the unexpected closes (segfaults)

[Regression Potential]

 * This patch is extremely cherry-picked, and is a one-line change.
Regression potential is near zero.

[Other Info]
 
 * This is a high priority bug.  This was fixed in 1.2.0.  Lack of an update in Precise to fix this bug will prevent the try_files directive from working correctly, which inhibits usage of nginx.

----------
----------

Original Bug Description:
-------

There's a known segfault in the "stable" version of nginx that is
included in Ubuntu Precise.

The upstream bug report: http://trac.nginx.org/nginx/ticket/152
The fix committed in the following changeset: http://trac.nginx.org/nginx/changeset/4601/nginx

Could you backport the fix or release a new version?

Thank you.

** Affects: nginx (Ubuntu)
     Importance: High
     Assignee: Michael Lustfield (michaellustfield)
         Status: Fix Released

** Affects: nginx (Ubuntu Precise)
     Importance: High
     Assignee: Thomas Ward (trekcaptainusa-tw)
         Status: In Progress

-- 
Known segfault in 1.1.19 (the current stable)
https://bugs.launchpad.net/bugs/1065555
You received this bug notification because you are a member of Ubuntu Sponsors Team, which is subscribed to the bug report.