[Bug 57844] New: Cannot submit new app version due to being blocked by cloudflare.

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=57844

Bug ID: 57844
           Summary: Cannot submit new app version due to being blocked by
                    cloudflare.
           Product: WineHQ Apps Database
           Version: unspecified
          Hardware: x86-64
                OS: Linux
            Status: UNCONFIRMED
          Severity: major
          Priority: P2
         Component: appdb-unknown
          Assignee: [e-mail]
          Reporter: [e-mail]
      Distribution: ArchLinux

Created attachment 78062
  --> https://bugs.winehq.org/attachment.cgi?id=78062
page I was redirected to

When I go and fill out a new version for some software (StudioTax), I get
through filling out the questionnaire, and then when I submit, I get blocked by
cloudflare.

Particularly infuriating because you lose all progress in what you submitted.

[Bug 57844] Cannot submit new app version due to being blocked by cloudflare.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=57844

Tom Maneiro  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[e-mail]

--- Comment #1 from Tom Maneiro  ---
Seems to be the same as bug 58194 - once you meet the Cloudflare challenge,
even if you pass it, your progress gets lot since the POST form data from the
application submit form has already been discarded by the challenge page.

This also breaks the feature to submit new applications too, not just new
versions or screenshots!

[Bug 57844] Cannot submit new app version due to being blocked by cloudflare.

[WineHQ Bugzilla]

http://bugs.winehq.org/show_bug.cgi?id=57844

Ken Sharp  changed:

What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|UNCONFIRMED                 |RESOLVED
         Resolution|---                         |DUPLICATE

--- Comment #2 from Ken Sharp  ---
Indeed the cause is the same so let's combine them.

*** This bug has been marked as a duplicate of bug 58194 ***