I think I'd still be in favor of allowing middleware to bypass the *just* the name length check (maybe up to twice the max_object_name_length or something?).
I think the concern with the abandoned patch was largely limited to metadata, and in particular the possibility of one middleware bypassing the check then passing the request along to another (broken) middleware that inserts way too much metadata.
I'd feel more comfortable bypassing the name length check because
* middlewares don't mess with path info much (swift3 and bulk upload are the only two exceptions I can think of off-hand) and
* as long as we still have *some* hard cap, the potential for abuse is fairly minimal.
I think I'd still be in favor of allowing middleware to bypass the *just* the name length check (maybe up to twice the max_object_ name_length or something?).
I think the concern with the abandoned patch was largely limited to metadata, and in particular the possibility of one middleware bypassing the check then passing the request along to another (broken) middleware that inserts way too much metadata.
I'd feel more comfortable bypassing the name length check because
* middlewares don't mess with path info much (swift3 and bulk upload are the only two exceptions I can think of off-hand) and
* as long as we still have *some* hard cap, the potential for abuse is fairly minimal.