I'm a bit late and Mohamed already gave you a solution that should work, I'd just like to point out -for additional clarity- that since this is encrypted traffic, you need to run both clientSSL and HTTP profiles on your service in order to perform content modification. If back-end servers expect encrypted packets, you should also use a serverSSL profile.
Also, I don't know how many paths your web service is running, but I usually script "exact matches" when I have this type of request, to avoid disrupting (possibly) similar pages in different folders that don't need to be redirected.
To achieve the URL redirection you described, you'll need to set up server-side redirects using your web server's configuration. The method may vary depending on your web server software. If you're using Nginx, you can use the provided configuration example with the necessary adjustments. If you have a different web server, refer to its documentation for redirection settings. Don't forget to back up your configuration file before making changes.
In summary, to achieve the URL redirection you want, set up server-side redirects based on your web server software. Use the provided Nginx configuration example if applicable, or consult your web server's documentation for redirection instructions. Always remember to back up your configuration file before making changes for added security.