Visitar URL original
Allow for disabling client-side validation in V4 Post Policy · Issue #1178 · googleapis/java-storage · GitHub
Skip to content
This repository was archived by the owner on Sep 25, 2026. It is now read-only.
This repository was archived by the owner on Sep 25, 2026. It is now read-only.

Allow for disabling client-side validation in V4 Post Policy #1178

Closed

Description

@frankyn

When calling validateFields; it checks to make sure provided input field keys are part of a known list. This is restrictive on input and would require an update if we introduce more fields in the future (which is possible).

Follow-up:

  • Does the server return a useful error?
  • Is the error state opaque such that the server can't return a better error?
  • If the server can be improved should we advocate that?
  • If the server error can only be opaque, do we want to introduce a strict/relaxed validation option? strict: throw exception or relaxed: log a warning for customer

Activity

  1. added
    priority: p2Moderately-important priority. Fix may not be included in next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    on Dec 14, 2021
  2. frankyn commented on Jan 10, 2022

    @frankyn
    ContributorAuthor

    @JesseLovelace are you still looking at this issue?

  3. JesseLovelace commented on Jan 20, 2022

    @JesseLovelace
    Contributor

    The server gives a 400 bad request with the following message:

    <?xml version='1.0' encoding='UTF-8'?><Error><Code>InvalidPolicyDocument</Code><Message>The content of the form does not meet the conditions specified in the policy document.</Message><Details>Invalid exact match name: invalid</Details></Error>
    

    This should be sufficient for debugging, so we'll remove the validation

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

api: storageIssues related to the googleapis/java-storage API.priority: p2Moderately-important priority. Fix may not be included in next release.type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.

Type

No type

Projects

No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions