Closed Nomad192 closed 1 year ago
@Nomad192 Sorry about the delayed response.
Can you please share why we need to add https://
?
@varunsridharan
!!! WARNING !!!
! I use google translate !
Before the fixes, I was getting an error like Invalid URL'example.com/api/v1/orgs ': No schema supplied. Perhaps you meant http://example.com/api/v1/orgs?
, I think it is necessary to support the situation when the user forgot to add http://
or https://
to his address in config.json
in the host
field.
To be honest, up to this point I thought it was a script bug. Now I realized that I just forgot to specify it in my `config.json'.
I will try to fix the PR after a while so that it matches the first paragraph.
Added
"https://" +
for all links!!! WARNING !!!
Bugfix
Correction of errors like "Invalid URL 'example.com/api/v1/orgs': No schema supplied. Perhaps you meant http://example.com/api/v1/orgs?"
The correction on
"http://" +
did not give the desired result, the source server works for reverse proxy on httpsTested on win 11 (x64) via cmd (administrator)