suggestions for redirecting https -> http and back

Hello !

I recently purchased a .app web domain which requires all traffic be https.
However I'm working on a project which access an api which only serves http
(http://football-data.org). This is causing mixed content errors.After a
bit of research, I am thinking to

···

--
A musician must make music, an artist must paint, a poet must write, if he
is to be ultimately at peace with himself.
- Abraham Maslow

Oops, sorry... okay back to the email ...

So, I recently purchased an .app web domain which requires all traffic be
https. However I'm working on a project which access an api which only
serves http (http://football-data.org). This is causing mixed content
errors.

After a bit of research, I am thinking to add a microservice to my site,
such that a) my main app calls the local server on a different url, and b)
that url is served by a different app, a microservice which will consume
the https request and make a separate http call to the football-data API,
receive the http response, convert back to https and serve the request. A
bit complicated, but it seems like the best solution on the web side.

A couple questions -- one, does this sound like the right approach? If so
two, would this be a good library to use for the microservice?

Any suggestions or experience would be greatly appreciated. Thanks !

···

On Fri, Jan 4, 2019 at 5:54 PM Sean Felipe Wolfe <ether.joe@gmail.com> wrote:

Hello !

I recently purchased a .app web domain which requires all traffic be
https. However I'm working on a project which access an api which only
serves http (http://football-data.org). This is causing mixed content
errors.After a bit of research, I am thinking to

--
A musician must make music, an artist must paint, a poet must write, if he
is to be ultimately at peace with himself.
- Abraham Maslow

--
A musician must make music, an artist must paint, a poet must write, if he
is to be ultimately at peace with himself.
- Abraham Maslow

Hello,

I think football-data.org actually supports https request. I tried to
access both their homepage (https://www.football-data.org/\) and some
resources (https://api.football-data.org/v2/competitions/ and
https://api.football-data.org/v2/players/44/matches\) through https, and it
works.

···

On Sat, Jan 5, 2019 at 9:57 AM Sean Felipe Wolfe <ether.joe@gmail.com> wrote:

Oops, sorry... okay back to the email ...

So, I recently purchased an .app web domain which requires all traffic be
https. However I'm working on a project which access an api which only
serves http (http://football-data.org). This is causing mixed content
errors.

After a bit of research, I am thinking to add a microservice to my site,
such that a) my main app calls the local server on a different url, and b)
that url is served by a different app, a microservice which will consume
the https request and make a separate http call to the football-data API,
receive the http response, convert back to https and serve the request. A
bit complicated, but it seems like the best solution on the web side.

A couple questions -- one, does this sound like the right approach? If so
two, would this be a good library to use for the microservice?
GitHub - jtrupiano/rack-rewrite: A web server agnostic rack middleware for defining and applying rewrite rules. In many cases you can get away with Rack::Rewrite instead of writing Apache mod_rewrite rules.

Any suggestions or experience would be greatly appreciated. Thanks !

On Fri, Jan 4, 2019 at 5:54 PM Sean Felipe Wolfe <ether.joe@gmail.com> > wrote:

Hello !

I recently purchased a .app web domain which requires all traffic be
https. However I'm working on a project which access an api which only
serves http (http://football-data.org). This is causing mixed content
errors.After a bit of research, I am thinking to

--
A musician must make music, an artist must paint, a poet must write, if
he is to be ultimately at peace with himself.
- Abraham Maslow

--
A musician must make music, an artist must paint, a poet must write, if he
is to be ultimately at peace with himself.
- Abraham Maslow

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

Hahaha .... I think this is the software equivalent of ... "did you check
if it's plugged in" ??

thanks :slight_smile:

···

On Fri, Jan 4, 2019 at 7:03 PM Tiancheng Luo <i@iltc.io> wrote:

Hello,

I think football-data.org actually supports https request. I tried to
access both their homepage (https://www.football-data.org/\) and some
resources (https://api.football-data.org/v2/competitions/ and
https://api.football-data.org/v2/players/44/matches\) through https, and
it works.

On Sat, Jan 5, 2019 at 9:57 AM Sean Felipe Wolfe <ether.joe@gmail.com> > wrote:

Oops, sorry... okay back to the email ...

So, I recently purchased an .app web domain which requires all traffic be
https. However I'm working on a project which access an api which only
serves http (http://football-data.org). This is causing mixed content
errors.

After a bit of research, I am thinking to add a microservice to my site,
such that a) my main app calls the local server on a different url, and b)
that url is served by a different app, a microservice which will consume
the https request and make a separate http call to the football-data API,
receive the http response, convert back to https and serve the request. A
bit complicated, but it seems like the best solution on the web side.

A couple questions -- one, does this sound like the right approach? If so
two, would this be a good library to use for the microservice?
GitHub - jtrupiano/rack-rewrite: A web server agnostic rack middleware for defining and applying rewrite rules. In many cases you can get away with Rack::Rewrite instead of writing Apache mod_rewrite rules.

Any suggestions or experience would be greatly appreciated. Thanks !

On Fri, Jan 4, 2019 at 5:54 PM Sean Felipe Wolfe <ether.joe@gmail.com> >> wrote:

Hello !

I recently purchased a .app web domain which requires all traffic be
https. However I'm working on a project which access an api which only
serves http (http://football-data.org). This is causing mixed content
errors.After a bit of research, I am thinking to

--
A musician must make music, an artist must paint, a poet must write, if
he is to be ultimately at peace with himself.
- Abraham Maslow

--
A musician must make music, an artist must paint, a poet must write, if
he is to be ultimately at peace with himself.
- Abraham Maslow

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

Unsubscribe: <mailto:ruby-talk-request@ruby-lang.org?subject=unsubscribe>
<http://lists.ruby-lang.org/cgi-bin/mailman/options/ruby-talk&gt;

--
A musician must make music, an artist must paint, a poet must write, if he
is to be ultimately at peace with himself.
- Abraham Maslow