826960 - Packaged App Validation always fails with a developer url specified against quality.mozilla.org

Status: RESOLVED FIXED

(Marketplace Graveyard :: Developer Pages, defect, P3)

Description

[Jason Smith [:jsmith]]

Steps:

1. Grab this zip file - https://github.com/jds2501/webapi-permissions-tests/blob/gh-pages/contactscreateonly.zip
2. Run that zip file through the validator

Expected:

We shouldn't fail due to the developer url doing a redirect from http://quality.mozilla.org to https://quality.mozilla.org.

Actual:

A validation error is thrown for the fact that the developer url does a redirect from http://quality.mozilla.org to https://quality.mozilla.org. I don't see why we would fail due to a redirect - shouldn't be allowed in the developer url?

Comment 1

[Jason Smith [:jsmith]]

Attachment: Test App

Comment 2

[Jason Smith [:jsmith]]

Just use the attached zip file for testing this - I'll be attaching a fix to the file on github that will work around this bug.

Comment 3

[Jason Smith [:jsmith]]

Well turns out the work-around I thought was going to work did not work at all.

Setting the dev url to https://quality.mozilla.org to avoid the redirect still reproduces the bug. So it looks like we might be failing in more cases than I initially expected.

Comment 4

[Jason Smith [:jsmith]]

Okay maybe it isn't always failing, but it appears to be failing with quality.mozilla.org.

Comment 5

[Matt Basta [:basta]]

This isn't a bug with the validator, it's a bug in zamboni.

Comment 6

[Wil Clouser [:clouserw]]

(In reply to Matt Basta [:basta] from comment #5)
> This isn't a bug with the validator, it's a bug in zamboni.

So, if someone were to change the summary of the bug would "App upload fails when developer URL 302s http to https" be appropriate?

Comment 7

[Matt Basta [:basta]]

(In reply to Wil Clouser [:clouserw] from comment #6)
> So, if someone were to change the summary of the bug would "App upload fails
> when developer URL 302s http to https" be appropriate?

Yeah. This might actually be a dupe of that bug that Kumar was working on with pyopenssl

Comment 8

[Christopher Van Wiemeersch [:cvan]]

Related: bug 875142 and bug 869518

Comment 9

[Wil Clouser [:clouserw]]

It is, bug 875142 blocks this one.  It's a P3, so marking this the same.

Comment 10

[Matt Basta [:basta]]

Bug 875142 is fixed, so this should be fine now.