Then, I would not check for protocol and domain in the string. What if it's using https? What if you move the app to a new domain? You should not have to change code when these occur. So just check the path part of the URL, not the whole URL.
Then, I'd set a variable (an enum might be nice with values like; BASE, MENS, WOMENS, and send that to the JSP.
JSP Rule of Thumb #1: make the JSP as stupid as possible. Do all the heavy work in the servlet controller.
What Bear said. There's a very good reason that Model/View/Controller (MVC) is the prevailing architecture for GUI applications, both web-based and otherwise. It's a LOT easier to maintain an application where the logic and the view are in separate components. It's also a lot easier to port such apps, and you also gain a lot of useful power. For example, one Model can be displayed in multiple views, such as a spreadsheet with matching chart. And conversely, a composite view can source from multiple models.
Also, when you have logic on both View and Model that interacts, it becomes a "treasure hunt" every time you need to find which file something is done in and changes to one object often breaks stuff in the other.
Then there's the practical fact that it's a son of a to debug logic on a View Template, such as a JSP. It's punitively difficult to set breakpoints and view/modify data for code in a JSP. Much better to put that stuff in a service class and use the normal debugger features.
An IDE is no substitute for an Intelligent Developer.