should ProxyHeadersMiddleware support ports in x-forwarded-for?

[dhduvall]

I have an x-forwarded-for header coming in, the value of which has the form ip1:port1,ip2,ip3. ip3 is the one I care about, so the first entry never matters, but the form is a thing, even if it's not very common. Should ProxyHeadersMiddleware strip the :port from any entry in the list? Or should I write another middleware that rewrites the header (assuming it ever becomes an issue)?