1016974 - Allow *.mozillaindia.org to request reps.mozilla.org API

Status: RESOLVED WORKSFORME

(Mozilla Reps Graveyard :: reps.mozilla.org, task)

Description

[Sudheesh Singanamalla (:ShellHacker)]

At Mozilla India, for easier collaboration within the community we are developing an events portal and plan to make it into a space for event owners to request volunteering Reps / Speakers from the Evangelism Task Force  / Technical Task Force to attend the event and speak.

Ongoing work : https://github.com/MozillaIndia/vibe
https://gist.github.com/sudheesh001/f9628b51810dbf4aebee

```
Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://reps.mozilla.org/api/v1/event/?offset=0&limit=0&start__gte=2014-5-28&query=india. This can be fixed by moving the resource to the same domain or enabling CORS.
```
Please allow *.mozillaindia.org among the following list which is allowed to request the content.

```
requests.exceptions.SSLError: hostname 'reps.mozilla.org' doesn't match either of 'generic-san.mozilla.org', 'inform.mozilla.org', 'air.mozilla.org', 'basket.mozilla.org', 'blog.mozilla.com', 'blog.mozilla.org', 'boardwiki.mozilla.org', 'creative.mozilla.org', 'foundationwiki.mozilla.org', 'join.mozilla.org', 'mpl.mozilla.org', 'outgoing.mozilla.org', 'quality.mozilla.org', 'securitywiki.mozilla.org', 'wiki.mozilla.org', 'tbpl.mozilla.org', 'basket.mozilla.com', 'air.mozilla.com', 'hacks.mozilla.org', 'brendaneich.com', 'www.brendaneich.com', 'dragnet.mozilla.org', 'www.itisatrap.org', 'itisatrap.org', 'calendar.mozilla.org', 'allizom.org', 'www.allizom.org', 'moztrap.mozilla.org'
```

Comment 1

[Giorgos Logiotatidis [:giorgos]]

Sudheesh,

Reps doesn't have a public API, which means that we don't guarantee that the API will not change, there is no documentation, neither we support clients like in this case. Therefore we will not do any of the changes you request.

I suggest that you reach out to us in reps-dev mailing list to discuss other ways to solve your problem in a proper way.

Comment 2

[Soumya Deb [:Debloper]]

Giorgos,

I do see quite a few even non-mozilla domains to have allow-origin access on reps' portal - can you please elaborate what might be the blocker for a well-developed community site to be able to use this data?

FWIW, the ask is not for an API (or the stability of it); just to be able to trump the CORS.
For which, Sudheesh' request seems pretty proper (unless Giorgos has hints how to preflight the request-headers which will work without having to add the domain to allow-origin list) ;)

Sudheesh: please start a discussion on the reps-dev list - I think you'll get a faster resolution there. Once you do, make sure to resolve this bug.

Comment 3

[Giorgos Logiotatidis [:giorgos]]

(In reply to Soumya Deb [:Debloper] from comment #2)
> Giorgos,
> 
> I do see quite a few even non-mozilla domains to have allow-origin access on
> reps' portal - can you please elaborate what might be the blocker for a
> well-developed community site to be able to use this data?

All these domains are configured for a reason which I honestly don't know. These domains where _not_ reconfigured for ReMo specifically but they are shared configuration with other m.o websites.

The blocker is that we have a _private_ API, therefore I don't suggest that you bind to the current API and we won't support the use of the API in any way, including to add CORS headers now or anything else that one can need in the future.

This has nothing to do with your community, on the contrary I personally want to help the community growth that's why I offer to examine other solutions.


> FWIW, the ask is not for an API (or the stability of it); just to be able to
> trump the CORS.

So you can use the API, correct?

All I'm saying is that we don't have a public API and therefore we will not support any requests regarding that non public API or it's use.


I'm happy to explore other solutions for your problem. 

If that answers your question please re-close the bug.

Comment 4

[Soumya Deb [:Debloper]]

Giorgos, we'll work around it then. No worries... ;)
Thanks for the valuable feedback - should've gotten the message earlier. :P

Comment 5

[Jai [:dolftax]]

Workaround: Vibe now uses JSONP - https://github.com/MozillaIndia/vibe/blob/gh-pages/js/script.js#L7