Fixed a nasty bug where non-existent objects that caused a Not Found
during resolve_url caused the exception method of the (cloned) response object to be called. This mean that as soon as an error occurred during resolve_url, the transaction would be aborted and things got extremely weird since objects that had been uncataloged would suddenly be back (due to the abort).
Showing
Please register or sign in to comment