Closed cambiata closed 4 years ago
Ah, I just noticed your TODO note in the source line above: 'consider putting protocol here'... :-)
You should choose the correct tink_http client, e.g. SecureJsClient
Oh - lots of things to discover..! Was so proud I found JsClient..! :-) Thanks!
The current
tink.web.proxy.Remote.hx
implementation prepends the outgoing request url with '//': https://github.com/haxetink/tink_web/blob/c6903306c69a766468adf19c3e329ac43c6308dd/src/tink/web/proxy/Remote.hx#L58This makes it impossible include the http protocol part in the host name when setting up a remoting endpoint. For me, this is causing problems when using remoting from a Firebase hosted app to functions driven server on the same domain:
mysite.firebaseapp.com
is resolved tohttp://mysite...
- should behttps://mysite...
https://mysite.firebaseapp.com
is resolved tohttp://https://mysite...
For now, I've hacked
tink.web.proxy.Remote.hx
to not prepend '//' to get around this.