[JIRA] Commented: (JOWS-37) FileBackedHttpResource does not properly read backup file, during initialization, if remote file is unreachable

Scott Cantor (JIRA) noreply at shibboleth.net
Fri Aug 10 21:15:06 EDT 2012


    [ https://issues.shibboleth.net/jira/browse/JOWS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316#comment-14316 ] 

Scott Cantor commented on JOWS-37:
----------------------------------

The normal case in a working system is a transitory failure, which is going to give you exactly a connection error, so that's definitely not a good choice to include in the "not exists" bucket.

I would never favor aggressively trying to detect configuration failures that would occur during the very early setup of the system vs. gracefully handling things that crop up all the time with a perfectly configured one.

And note that anybody that really wants it to fail hard has a simple solution: have their startup script archive or destroy any backup file(s) so that there is nothing to fall back to.

> FileBackedHttpResource does not properly read backup file, during initialization, if remote file is unreachable
> ---------------------------------------------------------------------------------------------------------------
>
>                 Key: JOWS-37
>                 URL: https://issues.shibboleth.net/jira/browse/JOWS-37
>             Project: OpenWS - Java
>          Issue Type: Bug
>          Components: Utilities
>    Affects Versions: 1.4.4
>            Reporter: Chad La Joie
>            Assignee: Chad La Joie
>            Priority: Minor
>
> The FileBackedHttpResource does not read, and return, the backup file if the remote file can not be read during installation.  This may be desired behavior in some cases but may not be in others.  Probably should have a flag to control this.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the commits mailing list