1336257 - Use of http://mozqa.com/ in m-c/source/services/sync/tests/tps/test_tabs.js

Status: RESOLVED FIXED

(Testing Graveyard :: TPS, defect)

Description

[:Atoll]

Hi, while reviewing mozqa usage in mozilla-central, we observed that there are two instances of http://mozqa.com/ in source/services/sync/tests/tps/test_tabs.js.

/*
 * Tab lists.
 */

var tabs1 = [
  { uri: "http://mozqa.com/data/firefox/layout/mozilla.html",
    title: "Mozilla",
    profile: "profile1"
...
var tabs2 = [
  { uri: "http://mozqa.com/data/firefox/layout/mozilla_community.html",
    title: "Mozilla Community",
    profile: "profile2"

I'd like to propose one of three replacement URL prefixes here:

1) http://no-ssl.mozqa.com/

If the URL *must* be a 200 OK url to valid content, and *must* be fetched over plain HTTP, then replace 'http://mozqa.com' with 'http://no-ssl.mozqa.com'. (This will require bug 1336254 to be completed first.)

2) https://nxdomain.mozqa.com/

If the URL *can* be invalid, and does not need to resolve nor retrieve any content, then replace 'http://mozqa.com' with 'https://nxdomain.mozqa.com'. This makes clear the intentions of this URL, as we explicitly would never offer service at 'nxdomain.mozqa.com', while permitting your tests to continue operating as expected.

3) https://mozqa.com/

If the URL *must* be a 200 OK url to valid content, but *may* be fetched over HTTPS, then replace 'http://mozqa.com' with 'https://mozqa.com'. This is available immediately and will remain working and supported.

(Setting needinfo? markh per my conversation with :whimboo.)

Comment 1

[Mark Hammond [:markh]]

I suspect we never actually visit those URLs. Thom, can you please verify that we don't care what those URLs are?

Comment 2

[Thom Chiovoloni [:tcsc] (please ni?)]

I think we'll load them and I'm not sure if we'll sync tabs for tabs that fail to load.

IMO we should just switch to HTTPS, no reason not to.

Comment 3

[Mark Hammond [:markh]]

(In reply to Thom Chiovoloni [:tcsc] from comment #2)
> I think we'll load them and I'm not sure if we'll sync tabs for tabs that
> fail to load.

Doh - thanks - for some reason I thought they were bookmarks!

> IMO we should just switch to HTTPS, no reason not to.

Agreed, thanks.

Comment 4

[:Atoll]

Excellent. I can help with a patch for option 3 if that's useful here, or otherwise it should be a simple change. Thank you!

Comment 5

[Mark Hammond [:markh]]

(In reply to Richard Soderberg [:atoll] from comment #4)
> Excellent. I can help with a patch for option 3 if that's useful here, or
> otherwise it should be a simple change. Thank you!

A patch would be very useful (and help ensure it doesn't slip off our radar!), thanks!

Comment 6

[Thom Chiovoloni [:tcsc] (please ni?)]

Attachment: Bug 1336257 - Use HTTPS for mozqa url in TPS.

Review commit: https://reviewboard.mozilla.org/r/204096/diff/#index_header
See other reviews: https://reviewboard.mozilla.org/r/204096/

Comment 7

[Mark Hammond [:markh]]

Comment on attachment 8933120 [details]
Bug 1336257 - Use HTTPS for mozqa url in TPS.

https://reviewboard.mozilla.org/r/204096/#review209574

Comment 8

[:Atoll]

Comment on attachment 8933120 [details]
Bug 1336257 - Use HTTPS for mozqa url in TPS.

This patch satisfies the needs of my original request differently than I expected, but is also completely fine.

Comment 9

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/integration/autoland/rev/d47bd8c2d39d
Use HTTPS for mozqa url in TPS. r=markh

Comment 10

[Cristian Brindusan [:cbrindusan]]

https://hg.mozilla.org/mozilla-central/rev/d47bd8c2d39d