Investigate http:base.domain vs. https:base.domain grid creation failure.

[BRONSOLO]

I've experienced that grid creation fails with the following error when my base domain is specified to use HTTP instead of HTTPS.

We should investigate why this occurred and look to add better handling of HTTP vs. HTTPS config file specifications.

Perhaps we should warn a user if they have specified HTTP?

@Kully @cldougl

[Kully]

Perhaps we should warn a user if they have specified HTTP?

How often do requests use HTTP over HTTPS anyways? If it's substantial then a warning might be a good idea. Coercing to HTTPS doesn't ever seem like a good idea to me.

[BRONSOLO]

@Kully no requests should be made over HTTP / all requests should be made over HTTPS.

[Kully]

@BRONSOLO in that case I can write either a warning as you suggested or an error message that pops up before the more vague Plotly Request error to give a heads up. WDYT?

[BRONSOLO]

an error message that pops up before the more vague Plotly Request error to give a heads up

I say go with the error message. @cldougl what do you think?

I think it would also be useful if someone could investigate/reproduce what I saw in the top comment re: the "Listing all files not supported" when making a POST request to the grid V2 create endpoint when HTTP is specified for the base/api domain in the config file. It might give us more insight into how best to handle this fix.

[cldougl]

+1 for error message

@Kully was able to reproduce on etest

[BRONSOLO]

Thanks @Kully and @cldougl!

@Kully - were you able to identify why the "Listing all files not supported" error occurred when the POST request to create a grid was made over HTTP?

[Kully]

@BRONSOLO No I didn't investigate why.

[BRONSOLO]

OK, I suppose it's not so necessary. I'm mostly just curious : )

[Kully]

closing as issue is fixed