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
{{ message }}
This repository has been archived by the owner on Nov 1, 2023. It is now read-only.
Setting a new CustomIpAddressParser() for Owin setup doesn't actually call the custom parser.
The bug exists in ThrottlingMiddleware, SetIdentity. this is missing a call to core.IpAddressParser.
Inside ThrottlingHandler, SetIdentity we see:
entry.ClientIp = core.GetClientIp(request).ToString();
but in ThrottlingMiddleware we see:
entry.ClientIp = request.RemoteIpAddress;
in order for this to work we need to setup a method or call to IpAddressParser so the overloaded method can be reached, like:
entry.ClientIp = core.GetOwinClientIp(request);
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Setting a new CustomIpAddressParser() for Owin setup doesn't actually call the custom parser.
The bug exists in ThrottlingMiddleware, SetIdentity. this is missing a call to core.IpAddressParser.
Inside ThrottlingHandler, SetIdentity we see:
entry.ClientIp = core.GetClientIp(request).ToString();
but in ThrottlingMiddleware we see:
entry.ClientIp = request.RemoteIpAddress;
in order for this to work we need to setup a method or call to IpAddressParser so the overloaded method can be reached, like:
entry.ClientIp = core.GetOwinClientIp(request);
The text was updated successfully, but these errors were encountered: