Bug 46767 - mod_jk to send DECLINED in case no fail-over tomcats available/configured
Summary: mod_jk to send DECLINED in case no fail-over tomcats available/configured
Status: NEW
Alias: None
Product: Tomcat Connectors
Classification: Unclassified
Component: mod_jk (show other bugs)
Version: unspecified
Hardware: All All
: P2 enhancement (vote)
Target Milestone: ---
Assignee: Tomcat Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-25 14:12 UTC by Dinesh Ilindra
Modified: 2019-06-16 14:40 UTC (History)
1 user (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dinesh Ilindra 2009-02-25 14:12:52 UTC
Current behavior:

By default we would do an lb fail-over or return an error page if no worker is left or no lb is involved.

Required behavior:

Optionally we could return DECLINE in all such cases or at least when no fail-over worker is left.
Comment 1 Christopher Schultz 2017-09-01 14:45:58 UTC
Remove inaccessible reference URL.

What does "return DECLINE" mean?
Comment 2 Dinesh Ilindra 2017-09-02 19:02:35 UTC
"return DECLINE" means that the httpd server can continue the request processing to the next possible option

For example, 

if uri "/app/*" is configured to goto mod_jk and there is an error occurred in mod_jk processing (could be any reason), then the 500 code is returned and httpd also passes the same 500 to the requester

no, the other option here is that if an error occurred in mod_jk processing, it sends DECLINE to httpd, so that if a static folder with name "/app" is present on the docroot, that contents will be served based on the uri

So, here the static content that is on httpd server docroot will act as failover pages for the dynamic content that was supposed to be returned by mod_jk in an error scenario, rather than to return a 500 page

Hope this detail is more clear.

- Dinesh