[
https://issues.apache.org/jira/browse/KNOX-3058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17891328#comment-17891328
]
ASF subversion and git services commented on KNOX-3058:
-------------------------------------------------------
Commit 0358054bcbcf643d7348d91891b48e67fedabf1b in knox's branch
refs/heads/dependabot/maven/org.apache.shiro-shiro-core-1.13.0 from Philip
Zampino
[ https://gitbox.apache.org/repos/asf?p=knox.git;h=0358054bc ]
KNOX-3058: Avoid 404 When Topology Is Being Redeployed (#929)
> Avoid 404 When Topology Is Being Redeployed
> -------------------------------------------
>
> Key: KNOX-3058
> URL: https://issues.apache.org/jira/browse/KNOX-3058
> Project: Apache Knox
> Issue Type: Improvement
> Components: Server
> Reporter: Philip Zampino
> Assignee: Philip Zampino
> Priority: Major
> Time Spent: 1h 50m
> Remaining Estimate: 0h
>
> While a topology is being redeployed, if it is requested, the client receives
> an HTTP 404 response. Most clients will not retry when receiving a 404, so
> the interaction will fail.
> If Knox were to respond with a more retry-friendly response (e.g., HTTP 503),
> then clients could overcome these small windows of unavailability with
> retries.
> The difficult part may be distinguishing topology removal from topology
> inactivity. I think a deleted topology should still result in a 404.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
