Convertigo 8.4.0 – Short URLs to Apps

Overview

Starting with Convertigo 8.4.0, projects created using the new 8.4.0 project template can be exposed through short, clean, root‑domain URLs.
This feature allows applications to be accessed directly from a dedicated domain (e.g., https://myapp.company.com) instead of long technical Convertigo paths.

This enhancement simplifies production routing, improves user experience, and reduces complexity when integrating Convertigo apps behind reverse proxies or API gateways.

What Problem Does This Solve?

Before version 8.4.0, Convertigo applications were only accessible through long URLs such as:

https://backend-apps.convertigo.net/convertigo/projects/marketplace/DisplayObjects/mobile/marketplace

These URLs:

• Exposed internal Convertigo routing structure

• Were difficult to integrate with external systems

• Were not user‑friendly

• Required additional configuration for SEO, bookmarks, or mobile deep‑linking

What the New Feature Provides

With Convertigo 8.4.0, you can now map a project to a short root-domain URL, for example:

https://marketplace.convertigo.com/marketplace

This is achieved through:

• A Convertigo 8.4.0 project template, which includes the new routing capabilities

• A reverse proxy configuration (Nginx, Traefik, Apache, cloud gateway, etc.)

• A dedicated domain or subdomain pointing to the Convertigo Engine

This makes the application appear as if it is served directly from its own domain.

How It Works

1. Convertigo 8.4.0 Project Template

The new template includes updated routing rules that allow the engine to serve the application from the root of a domain without relying on the /convertigo/projects/... path.

2. Reverse Proxy Configuration

A reverse proxy is required to:

• Terminate HTTPS

• Route the root path / of the domain to the Convertigo project

• Rewrite URLs so the application behaves as if it is hosted at the domain root

Typical reverse proxies supported:

• Nginx

• Traefik

• Apache HTTPD

• Cloud load balancers (AWS ALB, GCP Load Balancer, Azure Front Door, etc.)

3. Domain Mapping

Each application can be assigned its own domain or subdomain, such as:

• https://marketplace.company.com

• https://portal.company.com

• https://myapp.company.com

Example Configuration (Nginx)

Below is a simplified example of how a reverse proxy might be configured:

server {
    server_name marketplace.convertigo.com;

    location / {
        proxy_pass https://backend-apps.convertigo.net/convertigo/projects/marketplace/;
        proxy_set_header Host $host;
        proxy_set_header X-Real-IP $remote_addr;
    }
}

Note: The exact configuration depends on your infrastructure and security requirements.

Voici une version enrichie de ton article, incluant un deuxième exemple de configuration reverse proxy avec Apache HTTPD, rédigé dans le même style professionnel et cohérent avec la documentation précédente.

Additional Reverse Proxy Example – Apache HTTPD

Below is an example configuration using Apache HTTPD with the mod_proxy and mod_proxy_http modules enabled.
This setup exposes a Convertigo project through a short root‑domain URL such as:

https://marketplace.convertigo.com/marketplace

Apache HTTPD Configuration Example

<VirtualHost *:443>
    ServerName marketplace.convertigo.com

    # SSL configuration (example, adapt to your environment)
    SSLEngine on
    SSLCertificateFile /etc/ssl/certs/marketplace.crt
    SSLCertificateKeyFile /etc/ssl/private/marketplace.key

    # Ensure required modules are enabled:
    # a2enmod proxy proxy_http rewrite headers ssl

    # Preserve original host and client information
    ProxyPreserveHost On
    RequestHeader set X-Forwarded-Proto "https"
    RequestHeader set X-Forwarded-Port "443"

    # Reverse proxy to Convertigo Engine
    ProxyPass        "/" "https://backend-apps.convertigo.net/convertigo/projects/marketplace/"
    ProxyPassReverse "/" "https://backend-apps.convertigo.net/convertigo/projects/marketplace/"

    # Optional: static file caching rules
    <Location "/">
        Header unset ETag
        FileETag None
        Header set Cache-Control "max-age=0, no-cache, no-store, must-revalidate"
    </Location>
</VirtualHost>

Notes

• You must enable the following Apache modules:
  proxy, proxy_http, rewrite, headers, ssl

• SSL configuration depends on your environment (Let’s Encrypt, corporate PKI, etc.)

• The ProxyPreserveHost directive ensures Convertigo receives the correct domain name, which is important for routing and CORS.

• Adapt the backend URL to your Convertigo Engine endpoint.

Benefits

✔ Cleaner URLs

Applications are accessible through short, readable URLs.

✔ Easier Integration

External systems no longer need to handle long technical paths.

✔ Better User Experience

Improved readability for end users, mobile apps, and SEO.

✔ Simplified DevOps

Reverse proxy and gateway rules become easier to maintain.

✔ Production‑Ready Routing

Designed for enterprise environments with load balancers and multi‑node setups.

Requirements

Typical Use Cases

• Exposing a Convertigo app as a public web application

• Providing a clean URL for mobile deep‑linking

• Integrating with corporate portals or SSO providers

• Deploying multiple apps under different subdomains

• Migrating from legacy URLs to modern, user‑friendly routes

Example Before/After

Conclusion

The Short URLs to apps feature in Convertigo 8.4.0 is a major improvement for production deployments.
It enables clean, domain‑root routing for applications, simplifies infrastructure configuration, and enhances the overall user experience.

This feature is especially valuable for organizations deploying multiple Convertigo applications at scale, or those requiring professional, user‑friendly URLs.