Skip to Main Content
InterSystems Ideas
We love hearing from our users. Tell us what you want to see next and upvote ideas from the community.
* Bugs and troubleshooting should as usual go through InterSystems support.
Status Needs review
Created by Tani Frankel
Created on Jul 16, 2023

Allow the Web Gateway Installer to map all requests (not only csp/cls/cxw).

When the Web Gateway Installer configures the Web Server (IIS, Apache, etc.) to direct requests to the InterSystems server, it does so only to certain URLs with a clear InterSystems-related request (e.g. *.csp or *.cls), thus allowing the Web Server to continue serving other requests that might not be intended to be directed to an InterSystems server.

But in many cases the Web Server is indeed dedicated for an InterSystems server, in these kinds of cases it would be desired that the "out-of-the-box" behavior would be to map all request to be sent from the Web Server to the Web Gateway. (This is also true for example for REST request that don't even have an extension).

This will become especially important for when we start shipping our products without the Private Web Server (PWS) and people will rely on the Web Gateway installation to have an out-of-the-box working Management Portal (including static files) etc.

Suggesting that the Web Gateway installer will therefore either by default map all request to the Web Gateway (my personal preference, though admittedly not "backward consistent"), or at least offer this as an option.

    Jul 16, 2023

    Thank you for submitting the idea. The status has been changed to "Needs review".

    Stay tuned!

  • Admin
    Vadim Aniskin
    Oct 23, 2023

    @Tani Frankel, you have a comment on your idea. Please answer it to help your idea to be promoted.

    1 reply
  • Dmitry Maslennikov
    Jul 24, 2023

    WebGateway was always able to process any types of files, just with proper configuration on the webserver side

    Nothing is required for WebGateway

    1 reply