I spent a couple of days struggling with a bug in the Blog module (4.0.0) where clicking the "read more" link in the list of recent posting would lead to an infinite redirect loop.  I was able to work around it by turning off  "Show SEO friendly URL" in the module options.

The trigger of the problem is my institution's F5 Big-IP load balancer, behind which my web server must live.  It's configured so that an incoming web request will go first to the load balancer, which will rewrite the port with a high number, and then send the request on to the web server.  For example, it will rewrite http://example.com/default.aspx to http://example.com:12345/default.aspx.  The web server is configured to listen on the high-numbered port, instead of port 80.  The web server hosts multiple sites, each listening on a distinct high-numbered port.  They do this for failover, and easy migration of sites between servers.  This configuration is not too unusual, though we've been bitten by it a few times over the years when we forget this is going on.

The problem in the blog module is in ViewEntry.ascx.vb, starting at line 133.  The code verifies that the request URL matches the URL returned by BlogNavigateURL, and if not, sends a 301 redirect including an X-Blog-Redirect-reason header.  In my case, the URL as seen by the web server includes the high-numbered port.  The BlogNavigateURL function will return the URL without the port number, which is correct.  The code needs to make the URL comparison insensitive to the port number of the actual request.  There's a setting in the <appSettings> within web.config, UsePortNumber, that seems relevant here.  Maybe the logic should be to look at that setting, and if false, make a port-number-insentitive URL comparison.  (Though I think a port-number-insensitive comparison would be fine even when that setting is true.) I think that change would fix my problem, and let all of us behind load balancers enjoy SEO friendly URLs.

Thanks very much!