Skip to content

missing ContentEncodingRule::NotSpecified option #528

@Mr-Leshiy

Description

@Mr-Leshiy

Summary

Current implementation of the ContentEncodingRule validation rule type assumes that the content-encoding field should be present or been optional, which is not the case anymore.

Description

Modify the current implementation of the ContentTypeRule by making it like

#[derive(Debug)]
pub(crate) enum ContentEncodingRule {
   Specified {
               /// expected `content-encoding` field
            exp: ContentEncoding,
           /// optional flag for the `content-encoding` field
         optional: bool,
   },
    NotSpecified,
}

When its NotSpecified the content-encoding field should be empty and not present at all in the document

Metadata

Metadata

Assignees

Labels

squad: gatekeepersCatalyst App Backend, System Development & Integration Team

Type

Projects

Status

✅ Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions