URL pattern matching fails for default ports HTTP 80 and HTTPS 443

If Knox is setup on default ports (i.e. HTTP 80 or HTTPS 443) it will fail as URLs will not match due to missing ports in the URLs. This is caused by APIs in the servlet API that remove these ports from the URLs. This can also affect deployment scenarios where Knox itself is listening on non-default ports but is used behind a load balancer that is listening on a default port. This is because the original request URL presented to the load balancer is the URL user for matching and rewriting in Knox and that port will be removed if it is 80 or 443.