Importing app from Apache server just fails

[jkister]

I want to import an app from an apache web server. It just ain't working. Importing from github works fine.

The server sees no traffic at all if i try a non-https import url

The server does see traffic via an https import url, and the logs confirm that the file was sent/http 200.

I thought the problem might be that the Content-Type field was just text/plain-- i compared it to github which is text/plain; charset=utf-8. so i updated it on my side, but it made no difference.

the sent header looks like this:

HTTP/1.1 200 OK
Date: Thu, 27 Oct 2022 17:53:03 GMT
Server: Apache
Last-Modified: Thu, 27 Oct 2022 17:43:48 GMT
ETag: "3fe-5ec07aefbb374"
Accept-Ranges: bytes
Content-Length: 1022
X-Content-Type-Options: nosniff
X-Frame-Options: sameorigin
Content-Type: text/plain; charset=utf-8
Keep-Alive: timeout=5, max=100
Connection: Keep-Alive

In all cases, no errors are reported on the hubitat page and no text is loaded/replaced in the text area.

bug ? clue ?

[bertabcd1234]

Could it be a CORS issue or anything else mentioned here?

Import URL Requirements by Hubitat?

GitLab is suppose to be the Open Source version of GitHub so theoretically it should be allowed. I think how GitHub does it is via it's own rails that serves the raw content similar to how git pages work. I have found only 1 work around for private repos and its very clumsy at best. For public repos I think you could publish them like pages by editing .gitlab-ci.yml -- I'll have to check this first though.

[jkister]

@bertabcd1234

Could it be a CORS issue or anything else mentioned here?

Indeed. There is no CORS on the server, and I vote that Hubitat should not be demanding that field at all. That's pretty-- wrong.

Access-Control-Allow-Origin: *

should behave the same as not having that field at all.

I also vote for for a 'feature' to be added where there is an error/reason shown on the webpage if the url is not imported. plain-http and the non-cors field just silently fail.

@bravenel @bobbyD

[jkister]

The way I hacked this, by the way - since there is no CORS on the server - was just to go inside the VirtualHost and append that field any time a file is accessed out of my tmp directory:

 <VirtualHost *:443>
   ...
   <Directory /home/hostedsites/www.jeremykister.com/www/tmp>
     Header set Access-Control-Allow-Origin "*"
   </Directory>
 </VirtualHost>