Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AzureReader2 doesn't work with 404Plugin #28

Closed
lilith opened this issue Feb 22, 2013 · 4 comments
Closed

AzureReader2 doesn't work with 404Plugin #28

lilith opened this issue Feb 22, 2013 · 4 comments
Assignees
@JaredReisinger
Labels
bug
Milestone
V3.5

Comments

@lilith
Copy link
Member

lilith commented Feb 22, 2013

No description provided.

@lilith
Copy link
Member Author

lilith commented May 13, 2013

When a blob is not found in AzureReader2, the 404Plugin cannot rescue the situation.

@ghost ghost assigned JaredReisinger Nov 27, 2013
@JaredReisinger
Copy link
Contributor

Looks like CloudBlobClient.GetBlobReferenceFromServer() can throw a StorageException, but the call isn't inside a try/catch (to be converted to a 'false' response for FileExists().

@lilith
Copy link
Member Author

lilith commented Dec 11, 2013

Well, that's sufficiently simple I guess :)

@JaredReisinger
Copy link
Contributor

The virtual provider/file calling code could wrap all virtual handlers in a try/catch to ensure that exceptions don't kill the pipeline. It would have "fixed" this problem, but also might mask errors in the individual plugins.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JaredReisinger JaredReisinger

Labels
bug
Projects
None yet
Milestone
V3.5
Development

No branches or pull requests
2 participants
@lilith @JaredReisinger