You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The HTTP_REAL_IP header is not available in openshift (likely a difference between microk8s and openshift ingress implementation). We have substituted the FORWARDED_FOR header and anticipated seeing the list of intervening RPs (shown when you just dump request.META). When we fetch with get, we only get the first one. This happens to be the one we want but it's not clear a) why this happens and b) whether it will always work (i.e. will it always pick first and will first always be the one we want).
Need to investigate this behavior in openshift/django context and make sure that we always get the correct behavior (i.e. we record the users originating IP in some form, either alone or in a list containing the full proxy chain)
The text was updated successfully, but these errors were encountered:
The HTTP_REAL_IP header is not available in openshift (likely a difference between microk8s and openshift ingress implementation). We have substituted the FORWARDED_FOR header and anticipated seeing the list of intervening RPs (shown when you just dump request.META). When we fetch with get, we only get the first one. This happens to be the one we want but it's not clear a) why this happens and b) whether it will always work (i.e. will it always pick first and will first always be the one we want).
Need to investigate this behavior in openshift/django context and make sure that we always get the correct behavior (i.e. we record the users originating IP in some form, either alone or in a list containing the full proxy chain)
The text was updated successfully, but these errors were encountered: