Question: HTTPS everywhere...problem

Hi.
I know of (and I also support) the HTTPS everywhere campaign.

With that said...

I'm working on a software for a factory which will have:
- 1 server in a room, with a node server running on it
- many cellphones sending pictures
- no internet access, everything works within the same, closed network

Have you seen the problem?
I developed the thing in 2 days...now, I'm 4 days working on how to turn on
the cameras in the cellphones as they are accessing the service using the
serve's IP address (which, evidently, is not HTTPS).

This raised the question in my head. There shouldn't be at least an option?
Something like a "yes, I AM sure of what I am doing, now let me do it
please" option in browsers, perhaps a flag, perhaps a pattern...

The answers I got so far were "you can't do it with web technologies", and
I will not accept that answer as final.

So...any option? Shouldn't web technologies allow us to develop this kind
of software/service as well?

Do you know of any option/solution for such problem? I've been wasting my
time with cordova and ionic, tried some caches, remote debuggin...so far,
nothing.

I'm really disappointed with this...the thing is really cool, works so fine
and fast and then...I can't install it there because my own browser does
not trust my own software in my own cellphones closed in my own network
accessing my own server :/

I even tried generating a certificate for it, but the server ends up with
new IPs from time to time and, as it will be installed in different
factories and stores, making it a static ip is not a good option.

Thanks you very much for any idea or suggestion.

[ ]s

*--*

*Felipe N. Moura*
Web Developer, Google Developer Expert
<https://developers.google.com/experts/people/felipe-moura>, Founder of
BrazilJS <https://braziljs.org/> and Nasc <http://nasc.io/>.

Website:  http://felipenmoura.com / http://nasc.io/
Twitter:    @felipenmoura <http://twitter.com/felipenmoura>
Facebook: http://fb.com/felipenmoura
LinkedIn: http://goo.gl/qGmq
---------------------------------
*Changing  the  world*  is the least I expect from  myself!
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/032cb9b7/attachment.html>

Have you tried just serving via https using your own signed certificates?
That's an easy solution, right?

On Sat, Aug 4, 2018, 4:23 PM Felipe Nascimento de Moura <
felipenmoura at gmail.com> wrote:

> Hi.
> I know of (and I also support) the HTTPS everywhere campaign.
>
> With that said...
>
> I'm working on a software for a factory which will have:
> - 1 server in a room, with a node server running on it
> - many cellphones sending pictures
> - no internet access, everything works within the same, closed network
>
> Have you seen the problem?
> I developed the thing in 2 days...now, I'm 4 days working on how to turn
> on the cameras in the cellphones as they are accessing the service using
> the serve's IP address (which, evidently, is not HTTPS).
>
> This raised the question in my head. There shouldn't be at least an
> option? Something like a "yes, I AM sure of what I am doing, now let me do
> it please" option in browsers, perhaps a flag, perhaps a pattern...
>
> The answers I got so far were "you can't do it with web technologies", and
> I will not accept that answer as final.
>
> So...any option? Shouldn't web technologies allow us to develop this kind
> of software/service as well?
>
> Do you know of any option/solution for such problem? I've been wasting my
> time with cordova and ionic, tried some caches, remote debuggin...so far,
> nothing.
>
> I'm really disappointed with this...the thing is really cool, works so
> fine and fast and then...I can't install it there because my own browser
> does not trust my own software in my own cellphones closed in my own
> network accessing my own server :/
>
> I even tried generating a certificate for it, but the server ends up with
> new IPs from time to time and, as it will be installed in different
> factories and stores, making it a static ip is not a good option.
>
> Thanks you very much for any idea or suggestion.
>
> [ ]s
>
> *--*
>
> *Felipe N. Moura*
> Web Developer, Google Developer Expert
> <https://developers.google.com/experts/people/felipe-moura>, Founder of
> BrazilJS <https://braziljs.org/> and Nasc <http://nasc.io/>.
>
> Website:  http://felipenmoura.com / http://nasc.io/
> Twitter:    @felipenmoura <http://twitter.com/felipenmoura>
> Facebook: http://fb.com/felipenmoura
> LinkedIn: http://goo.gl/qGmq
> ---------------------------------
> *Changing  the  world*  is the least I expect from  myself!
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/9c75f307/attachment.html>

Oh sorry you said you tried that. Apologies. Maybe resolving to a dedicated
Domain/Host?

On Sat, Aug 4, 2018, 5:40 PM Mark <mark at heyimmark.com> wrote:

> Have you tried just serving via https using your own signed certificates?
> That's an easy solution, right?
>
> On Sat, Aug 4, 2018, 4:23 PM Felipe Nascimento de Moura <
> felipenmoura at gmail.com> wrote:
>
>> Hi.
>> I know of (and I also support) the HTTPS everywhere campaign.
>>
>> With that said...
>>
>> I'm working on a software for a factory which will have:
>> - 1 server in a room, with a node server running on it
>> - many cellphones sending pictures
>> - no internet access, everything works within the same, closed network
>>
>> Have you seen the problem?
>> I developed the thing in 2 days...now, I'm 4 days working on how to turn
>> on the cameras in the cellphones as they are accessing the service using
>> the serve's IP address (which, evidently, is not HTTPS).
>>
>> This raised the question in my head. There shouldn't be at least an
>> option? Something like a "yes, I AM sure of what I am doing, now let me do
>> it please" option in browsers, perhaps a flag, perhaps a pattern...
>>
>> The answers I got so far were "you can't do it with web technologies",
>> and I will not accept that answer as final.
>>
>> So...any option? Shouldn't web technologies allow us to develop this kind
>> of software/service as well?
>>
>> Do you know of any option/solution for such problem? I've been wasting my
>> time with cordova and ionic, tried some caches, remote debuggin...so far,
>> nothing.
>>
>> I'm really disappointed with this...the thing is really cool, works so
>> fine and fast and then...I can't install it there because my own browser
>> does not trust my own software in my own cellphones closed in my own
>> network accessing my own server :/
>>
>> I even tried generating a certificate for it, but the server ends up with
>> new IPs from time to time and, as it will be installed in different
>> factories and stores, making it a static ip is not a good option.
>>
>> Thanks you very much for any idea or suggestion.
>>
>> [ ]s
>>
>> *--*
>>
>> *Felipe N. Moura*
>> Web Developer, Google Developer Expert
>> <https://developers.google.com/experts/people/felipe-moura>, Founder of
>> BrazilJS <https://braziljs.org/> and Nasc <http://nasc.io/>.
>>
>> Website:  http://felipenmoura.com / http://nasc.io/
>> Twitter:    @felipenmoura <http://twitter.com/felipenmoura>
>> Facebook: http://fb.com/felipenmoura
>> LinkedIn: http://goo.gl/qGmq
>> ---------------------------------
>> *Changing  the  world*  is the least I expect from  myself!
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/9bde3d27/attachment-0001.html>

> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <felipenmoura at gmail.com> a écrit :
> 
> I know of (and I also support) the HTTPS everywhere campaign.
> 

I don’t think that ECMAScript has any feature related to the http protocol, or that make a distinction between secure and non-secure contexts. Wrong mailing list?

—Claude
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180805/01c08db1/attachment.html>

Well, I read it in the some doumentation about it and the logged error
message was informing about this.
But indeed, the ES documentation is not mandatory about it. I'm trying
contact with people from the Chrome devtools about it.
I just realized it works in Firefox on Android...is a small limitation but
is some hope!

About the local domain suggested by Mark, I will have to check the
availability to configure a dedicated DNS server there...this is also an
interesting possibility.

So, as for the ES definitions, this is not a rule to be applied in all
browsers in a near future?

Thanks.

[ ]s

*--*

*Felipe N. Moura*
Web Developer, Google Developer Expert
<https://developers.google.com/experts/people/felipe-moura>, Founder of
BrazilJS <https://braziljs.org/> and Nasc <http://nasc.io/>.

Website:  http://felipenmoura.com / http://nasc.io/
Twitter:    @felipenmoura <http://twitter.com/felipenmoura>
Facebook: http://fb.com/felipenmoura
LinkedIn: http://goo.gl/qGmq
---------------------------------
*Changing  the  world*  is the least I expect from  myself!


On Sat, Aug 4, 2018 at 7:08 PM Claude Pache <claude.pache at gmail.com> wrote:

>
> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <felipenmoura at gmail.com>
> a écrit :
>
> I know of (and I also support) the HTTPS everywhere campaign.
>
>
> I don’t think that ECMAScript has any feature related to the http
> protocol, or that make a distinction between secure and non-secure
> contexts. Wrong mailing list?
>
> —Claude
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/30215057/attachment-0001.html>

I am not sure off the top of my head which officially require it in the
spec, but I know a lot of more recent APIs, including service worker, push
notifications, and geolocation, require HTTPS in some or all modern
browsers, and I know at least the Chrome team plans to require HTTPS for
more APIs in the future.

Zachary Yaro

On Sat, Aug 4, 2018, 18:08 Claude Pache <claude.pache at gmail.com> wrote:

>
> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <felipenmoura at gmail.com>
> a écrit :
>
> I know of (and I also support) the HTTPS everywhere campaign.
>
>
> I don’t think that ECMAScript has any feature related to the http
> protocol, or that make a distinction between secure and non-secure
> contexts. Wrong mailing list?
>
> —Claude
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/7646d47e/attachment.html>

All of those are browser, not ES, apis.

On Sat, Aug 4, 2018, 16:47 Zachary Yaro <zmyaro at gmail.com> wrote:

> I am not sure off the top of my head which officially require it in the
> spec, but I know a lot of more recent APIs, including service worker, push
> notifications, and geolocation, require HTTPS in some or all modern
> browsers, and I know at least the Chrome team plans to require HTTPS for
> more APIs in the future.
>
> Zachary Yaro
>
> On Sat, Aug 4, 2018, 18:08 Claude Pache <claude.pache at gmail.com> wrote:
>
>>
>> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <
>> felipenmoura at gmail.com> a écrit :
>>
>> I know of (and I also support) the HTTPS everywhere campaign.
>>
>>
>> I don’t think that ECMAScript has any feature related to the http
>> protocol, or that make a distinction between secure and non-secure
>> contexts. Wrong mailing list?
>>
>> —Claude
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/c2461067/attachment.html>

Oh, fair point.

Zachary Yaro

On Sat, Aug 4, 2018, 18:50 Peter Jaszkowiak <p.jaszkow at gmail.com> wrote:

> All of those are browser, not ES, apis.
>
> On Sat, Aug 4, 2018, 16:47 Zachary Yaro <zmyaro at gmail.com> wrote:
>
>> I am not sure off the top of my head which officially require it in the
>> spec, but I know a lot of more recent APIs, including service worker, push
>> notifications, and geolocation, require HTTPS in some or all modern
>> browsers, and I know at least the Chrome team plans to require HTTPS for
>> more APIs in the future.
>>
>> Zachary Yaro
>>
>> On Sat, Aug 4, 2018, 18:08 Claude Pache <claude.pache at gmail.com> wrote:
>>
>>>
>>> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <
>>> felipenmoura at gmail.com> a écrit :
>>>
>>> I know of (and I also support) the HTTPS everywhere campaign.
>>>
>>>
>>> I don’t think that ECMAScript has any feature related to the http
>>> protocol, or that make a distinction between secure and non-secure
>>> contexts. Wrong mailing list?
>>>
>>> —Claude
>>> _______________________________________________
>>> es-discuss mailing list
>>> es-discuss at mozilla.org
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/b4b11987/attachment.html>

Thanks then.
I'm gonna focus on discussing it with browsers vendors.

Cheers.

[ ]s

*--*

*Felipe N. Moura*
Web Developer, Google Developer Expert
<https://developers.google.com/experts/people/felipe-moura>, Founder of
BrazilJS <https://braziljs.org/> and Nasc <http://nasc.io/>.

Website:  http://felipenmoura.com / http://nasc.io/
Twitter:    @felipenmoura <http://twitter.com/felipenmoura>
Facebook: http://fb.com/felipenmoura
LinkedIn: http://goo.gl/qGmq
---------------------------------
*Changing  the  world*  is the least I expect from  myself!


On Sat, Aug 4, 2018 at 7:55 PM Zachary Yaro <zmyaro at gmail.com> wrote:

> Oh, fair point.
>
> Zachary Yaro
>
> On Sat, Aug 4, 2018, 18:50 Peter Jaszkowiak <p.jaszkow at gmail.com> wrote:
>
>> All of those are browser, not ES, apis.
>>
>> On Sat, Aug 4, 2018, 16:47 Zachary Yaro <zmyaro at gmail.com> wrote:
>>
>>> I am not sure off the top of my head which officially require it in the
>>> spec, but I know a lot of more recent APIs, including service worker, push
>>> notifications, and geolocation, require HTTPS in some or all modern
>>> browsers, and I know at least the Chrome team plans to require HTTPS for
>>> more APIs in the future.
>>>
>>> Zachary Yaro
>>>
>>> On Sat, Aug 4, 2018, 18:08 Claude Pache <claude.pache at gmail.com> wrote:
>>>
>>>>
>>>> Le 4 août 2018 à 22:22, Felipe Nascimento de Moura <
>>>> felipenmoura at gmail.com> a écrit :
>>>>
>>>> I know of (and I also support) the HTTPS everywhere campaign.
>>>>
>>>>
>>>> I don’t think that ECMAScript has any feature related to the http
>>>> protocol, or that make a distinction between secure and non-secure
>>>> contexts. Wrong mailing list?
>>>>
>>>> —Claude
>>>> _______________________________________________
>>>> es-discuss mailing list
>>>> es-discuss at mozilla.org
>>>> https://mail.mozilla.org/listinfo/es-discuss
>>>>
>>> _______________________________________________
>>> es-discuss mailing list
>>> es-discuss at mozilla.org
>>> https://mail.mozilla.org/listinfo/es-discuss
>>>
>> _______________________________________________
>> es-discuss mailing list
>> es-discuss at mozilla.org
>> https://mail.mozilla.org/listinfo/es-discuss
>>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20180804/dad2e530/attachment-0001.html>