Open drdreff opened 4 years ago
is it because "24.23.134.119:43398" is not a valid internet address? Perhaps it should be: "24.23.134.119" ?
That string is invalid, yes. I'm trying to trace back where in the proxy configuration the port number (43398
) is being added. I'm not sure if the fix belongs in drf-tracking or ... ? The symptom is that drf-tracking somewhat silently fails.
Just to let you know that this project has moved over to: https://github.com/lingster/drf-api-tracking as the original owner does not appear to be maintaining this. If you'd like me to take a deeper dive, can you raise an issue in the new repo?
The stack trace does point to an issue with drf-tracking. Do you have details of the request and query string that you could share to help reproduce the issue?
I will try to create a good test since I've only been getting this in Azure. I'l also head over to the new project
MD
Ok great, we're holding an online sprint(https://www.meetup.com/Python-Sprints/events/269207483/) to hopefully address some of the issues in the drf-api-tracking project. If you get your test ready before monday, then I'm sure there maybe some able to help resolve the issue.
please let me know what other help I can provide to help address this. I'd love to find a solution or workaround.
I'd really like to figure out a workaround for this issue. I'll put what I find here for others.