Bug 72 - LocationServer sometimes rejects a call even if StaticRoute or PyRoute provided routes
Summary: LocationServer sometimes rejects a call even if StaticRoute or PyRoute provid...
Status: NEW
Alias: None
Product: repro
Classification: Unclassified
Component: proxy (show other bugs)
Version: unspecified
Hardware: All All
: P1 major
Assignee: Owner of all unassigned bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-02-28 03:43 CST by Daniel Pocock
Modified: 2014-02-28 03:43 CST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Daniel Pocock 2014-02-28 03:43:29 CST
If LocationServer thinks the original request URI is an unknown user, it will reject a call, even if StaticRoute or PyRoute provided destinations where the call should be routed.

The setting

 ContinueProcessingAfterRoutesFound = false

works around this for the StaticRoute monkey, but maybe it also needs some adaption in the LocationServer monkey too.

The code in question is in the block with the comment "If A1 is empty, then user does not exist - return 404"