https://issues.apache.org/bugzilla/show_bug.cgi?id=35981
--- Comment #5 from Alejandro Alvarez <[email protected]> 2011-05-31 12:18:20 UTC --- Probably yes, as other calls need to be called in that case (seek, write, close), and 20x statuses are already managed by mod_dav. I suppose just a condition like this would do: if ((err = (*resource->hooks->open_stream)(resource, mode, &stream)) != NULL) { int status = err->status ? err->status : HTTP_FORBIDDEN; if (status > 299) err = dav_push_error(r->pool, status, 0, apr_psprintf(r->pool, "Unable to PUT new contents for %s.", ap_escape_html(r->pool, r->uri)), else err = NULL } True unexpected return codes may result. But I would say that's the developer's problem, not mod_dav's Any hope of this being fixed? -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
