Idea ID: 2690085

Remove VTS Port number from URL and have it as a query string

Status: Delivered

The current implementation of VTS involves http://<VTSMachineName>:<VTSportNumber>

The security setup in our current DMZ does not allow any incoming request which are not on port 80 or 443 (HTTP & HTTPS).. This is an issue where we have 300-400 VTS ports to run all our performance tests.

The request is to have the port as query based string..

Ex:

http://<VTSMachineName>:80/?portnumber=<VTS Port Number>

https://<VTSMachineName>:443/?portnumber=<VTS Port Number>

 

This will be beneficial for us as we can use Microfocus hosted external LGs (London, Frankfurt, Toronto) and these LGs use VTS machines which are hosted within our private Cloud infrastructure.

 

 

 

 

 

 

  • Do you know if this method would work with Apache HTTP Server using Mod_Proxy?  I'm trying this method, but I am uncertain what the configuration should be. Any ideas?

  • We will update the Nginx web server config file in the help center, which should fix the UI resources issue:

     

    worker_processes  1;
    
    events {
        worker_connections  1024;
    }
    
    http {
        include       mime.types;
        default_type  application/octet-stream;
    
        sendfile        on;
    
        keepalive_timeout  65;
    
    	server {
            listen  80;
            server_name  localhost;
        
            location / {
                if ($query_string ~* ^portnumber=(\d+)(.*)$) {
                	set $port $1;
                	set $para $2;
                	proxy_pass http://127.0.0.1:$port$para;
                } 
                proxy_pass http://127.0.0.1:4000;
                proxy_socket_keepalive on;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
        
            }	
            proxy_socket_keepalive on;
        }
    
        server {
            listen  443 ssl;
            server_name  localhost;
            ssl_certificate     "/opt/MF/MF_VTS/web/vts.crt";
            ssl_certificate_key "/opt/MF/MF_VTS/web/vts.key";
            ssl_protocols       TLSv1.2 TLSv1.3;
            ssl_ciphers         HIGH:!aNULL:!MD5;
        
            location / {
                if ($query_string ~* ^portnumber=(\d+)(.*)$) {
                	set $port $1;
                	set $para $2;
                	proxy_pass https://127.0.0.1:$port$para;
                } 
                proxy_pass https://127.0.0.1:4000;
                proxy_socket_keepalive on;
                proxy_http_version 1.1;
                proxy_set_header Upgrade $http_upgrade;
                proxy_set_header Connection "upgrade";
            }
        }
    }

  • This request has been addressed as mentioned above, if there are gaps in functionality or product issues, suggest to open a new idea request or to submit a support case. 

    Thanks 

  • I am also facing same issue, after implementing Nginx VTS GUI is not loading completely.
  • The CSS & JS links are not resolved automatically and tend to work if the links that failed with HTTP 500 are updated to point to the host.name/?portnumber=4444. 

    How to ensure the CSS, JS & other supportive files used by VTS to render the GUI is loaded properly after NGINX is configures?