I'm glad you brought that up. That's the one thing I didn't think about. We are inside a network that was recently updated. That update had messed up a different redirect to where it works outside the network but not inside. This is probably related to that issue.