#441: Put product request handlers in the right context
-------------------------+-------------------------------------------------
Reporter: olemis | Owner: olemis
Type: task | Status: accepted
Priority: critical | Milestone: Release 6
Component: | Version:
multiproduct | Keywords: product environment request handler
Resolution: | bep-0003
-------------------------+-------------------------------------------------
Description changed by olemis:
Old description:
> Embed product dispatching loop inside the global handler loop . This
> might also include considering `[trac]` `default_handler` setting to
> choose product landing page and preload settings to make product
> dashboard view the default .
>
> PS: Embedding won't be needed in sub-domain deployments as URL namespaces
> will not interfere .
New description:
This ticket encloses the following subtasks :
- Do not embed product dispatching loop inside the global
handler loop (as before) . Instead show a warning message
in ''HTTP 404 Not Found'' response .
* Embedding won't be needed in sub-domain deployments
as URL namespaces will not interfere
* [ticket:357 Environment factories] will put requests in the right
context.
- Consider `[trac]` `default_handler` setting to choose product landing
page.
Preload settings to make product dashboard view the default .
- Tweak environment factories
* Path match is not appropriate in sub-domain deployments
--
--
Ticket URL: <https://issues.apache.org/bloodhound/ticket/441#comment:6>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound issue tracker
