Consider having a way to disable all specification enforcements for attributes #207

New issue

Open

opened 2025-02-07 12:09:33 +00:00 by alexvanin · 1 comment

alexvanin commented

2025-02-07 12:09:33 +00:00

Owner

#174 and #197 enforce special treatment for FilePath and FileName attributes:

FilePath must start with a /
FileName must not start with a /

Consider having a way to override this behaviour when user wants to access object with invalid FilePath or FileName attribute.

Based on #205 (comment)

#174 and #197 enforce special treatment for `FilePath` and `FileName` attributes: * FilePath must start with a `/` * FileName must not start with a `/` Consider having a way to override this behaviour when user wants to access object with _invalid_ FilePath or FileName attribute. Based on https://git.frostfs.info/TrueCloudLab/frostfs-http-gw/pulls/205#issuecomment-66750

alexvanin referenced this issue

2025-02-07 12:09:46 +00:00

174-add_slash_clipping_when_search_by_filename_attr_master #205

r.loginov commented

2025-02-07 13:19:44 +00:00

Member

I would like to clarify. When doing a fallback by FileName attribute search, do we also want to be able to apply without checks? Or do we not change the fallback?

I would like to clarify. When doing a [fallback by FileName attribute search](https://git.frostfs.info/TrueCloudLab/frostfs-http-gw/src/branch/master/internal/handler/handler.go#L301), do we also want to be able to apply without checks? Or do we not change the fallback?

alexvanin changed title from ~~Consider having a way to disalbe all specification enforcements for attributes~~ to Consider having a way to disable all specification enforcements for attributes

2025-02-07 13:25:33 +00:00