Bug: JS Tracker is logging port numbers incorrectly

For engineers Enrichment
1

Hello,

@jon-ga have identified an issue with a JS tracker that incorrectly identifies (defaults to) 80 as a port for https / TLS urls. Since browsers strip default port numbers from the url (80/http , 443/https) JS tracker seems to try to assign a default. It seems tracker makes no distinction between http and https schemas when it does that.

2 Likes
2

This is in common enrich rather than the Javascript tracker.

I’ve created an issue to track it as well as a PR that solves the issue.

3

Thanks @dashirov and @mike! We will get this fix rolled out in an upcoming release.