Skip to main content

Table of Contents

Moving the * URL pattern between servlets

The * is a wildcard character that is not used in the URL. * is the default servlet URL pattern that you can replace with another servlet.

Moving the * is optional and is done to change to the default and set up automatic redirection. For example, if one of your teams decides to move the * from default WebStandard to DeltaTeam, all access is automatically redirected from to by default.

If a request is received that does not match any of the defined URL patterns, then the definition for * is used to determine to what servlet the request is dispatched.

If you access something after /prweb and the servlet is not found, you are redirected to the default servlet, where * is configured as the URL pattern.

If the * URL pattern is not provided, then system becomes inaccessible. * is the minimum servlet requirement for a servlet to be accessible. Without *, the servlet produces a 403 error. The Servlet Management landing page provides a validation to ensure that at least one servlet is in the Enabled state with * as the URL pattern.

  1. Access the servlet from which you want to move the * URL pattern:

    1. In the header of Dev Studio, click Configure System Settings Servlet Management .

    2. Identify the servlet from which you want to remove the * URL pattern, click the More icon on the right side of the window, and then select Configure.

    3. Under URL patterns, click the delete icon beside the * URL pattern.

    4. Click Update.

  2. Add the * URL pattern to the servlet that you want to update:

    1. Identify the servlet to which you want to add the * URL pattern, click the More icon on the right side of the window, and then select Configure.

    2. Under URL patterns, click Add.

    3. Enter the * URL pattern.

    4. Click Update.

    5. For the changes to take effect, you must restart your entire environment.

To request a restart of the entire environment, select New request in My Support Portal. For more information, see:
Did you find this content helpful?

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us