Not setting apiBase in the interceptor?

I’m submitting a…

• Regression (a behavior that used to work and stopped working in a new release)
• Bug report
• Performance issue
• Feature request
• Documentation issue or request
• Other… Please describe:

Current behavior

With the apiBase set, it’s not prepending it to the path in HTTP calls. E.g. if I call this.http.get('foo').subscribe(...) I see a call to http://localhost:4200/foo. If specify the full path, e.g. this.http.get('http://myurl.com/foo') it works fine.

Expected behavior

The value of apiBase is prepended to the path in the interceptor.

What is the motivation / use case for changing the behavior?

This is how this used to work in the previous versions. If something changed in how this is expected to work, none of the docs have been updated.

Environment

Angular-Token version: 6.0.2 Angular version: 6.1.1

Bundler

• Angular CLI (Webpack)
• Webpack
• SystemJS

Browser:

• Chrome (desktop) version 68.0.3440.106
• Chrome (Android) version XX
• Chrome (iOS) version XX
• Firefox version XX
• Safari (desktop) version XX
• Safari (iOS) version XX
• IE version XX
• Edge version XX

Others:

[arjenbrandenburgh]

@misham The apiBase is indeed for the auth paths, but also as a security measure. The token headers are only added to calls going to the apiBase server.

[misham]

One other update, sign in & sign out plus all the “built-in” functions around auth work just fine. Only the interceptor is not working for some reason.