LIGHT

  • News
  • Docs
  • Community
  • Reddit
  • GitHub

URL Rewrite Rule

When we use the light-router as a gateway, the incoming URL might have a different path than the outgoing URL. To support it, you can add a section called urlRewriteRules in the router.yml to define a list of regex and replacement pairs.

Here is an example of the configuration for the UNIT tests.

# URL rewrite rules, each line will have two parts: the regex patten and replace string separated
# with a space. The light-router has service discovery for host routing, so whe working on the
# url rewrite rules, we only need to create about the path in the URL.
# Test your rules at https://www.freeformatter.com/java-regex-tester.html#ad-output
urlRewriteRules:
  # test your regex rule at https://www.freeformatter.com/java-regex-tester.html#ad-output
  # /listings/123 to /listing.html?listing=123
  - /listings/(.*)$ /listing.html?listing=$1
  # /ph/uat/de-asia-ekyc-service/v1 to /uat-de-asia-ekyc-service/v1
  - /ph/uat/de-asia-ekyc-service/v1 /uat-de-asia-ekyc-service/v1
  # /tutorial/linux/wordpress/file1 to /tutorial/linux/cms/file1.php
  - (/tutorial/.*)/wordpress/(\w+)\.?.*$ $1/cms/$2.php
  # used in the test case to router /v3/address request to /v2/address
  - /v3/(.*)$ /v2/$1

In the embedded router.yml, we have made this config property a template so that you can overwrite values in the values.yml file.

# URL rewrite rules, each line will have two parts: the regex patten and replace string separated
# with a space. The light-router has service discovery for host routing, so whe working on the
# url rewrite rules, we only need to create about the path in the URL.
# Test your rules at https://www.freeformatter.com/java-regex-tester.html#ad-output
urlRewriteRules: ${router.urlRewriteRules:}

The corresponding values.yml can have a section like the following.

router.urlRewriteRules:
  # test your regex rule at https://www.freeformatter.com/java-regex-tester.html#ad-output
  # /listings/123 to /listing.html?listing=123
  - /listings/(.*)$ /listing.html?listing=$1
  # /ph/uat/de-asia-ekyc-service/v1 to /uat-de-asia-ekyc-service/v1
  - /ph/uat/de-asia-ekyc-service/v1 /uat-de-asia-ekyc-service/v1
  # /tutorial/linux/wordpress/file1 to /tutorial/linux/cms/file1.php
  - (/tutorial/.*)/wordpress/(\w+)\.?.*$ $1/cms/$2.php
  # used in the test case to router /v3/address request to /v2/address
  - /v3/(.*)$ /v2/$1


The rule is written as a string with two parts. The first part is the regex pattern and the second part is the replacement whent he pattern is matched. If one of the rules is matched in the list, the source and target path should be the same.

The following is a very good online Java regex tester to verify your URL rewrite rules. Please be aware, we have other config files to handle the host routing so the URL rewrite rules will only apply to the path parameters. That is why you don’t see the host in the above sample rules.

  • About Light
    • Overview
    • Testimonials
    • What is Light
    • Features
    • Principles
    • Benefits
    • Roadmap
    • Community
    • Articles
    • Videos
    • License
    • Why Light Platform
  • Getting Started
    • Get Started Overview
    • Environment
    • Light Codegen Tool
    • Light Rest 4j
    • Light Tram 4j
    • Light Graphql 4j
    • Light Hybrid 4j
    • Light Eventuate 4j
    • Light Oauth2
    • Light Portal Service
    • Light Proxy Server
    • Light Router Server
    • Light Config Server
    • Light Saga 4j
    • Light Session 4j
    • Webserver
    • Websocket
    • Spring Boot Servlet
  • Architecture
    • Architecture Overview
    • API Category
    • API Gateway
    • Architecture Patterns
    • CQRS
    • Eco System
    • Event Sourcing
    • Fail Fast vs Fail Slow
    • Integration Patterns
    • JavaEE declining
    • Key Distribution
    • Microservices Architecture
    • Microservices Monitoring
    • Microservices Security
    • Microservices Traceability
    • Modular Monolith
    • Platform Ecosystem
    • Plugin Architecture
    • Scalability and Performance
    • Serverless
    • Service Collaboration
    • Service Mesh
    • SOA
    • Spring is bloated
    • Stages of API Adoption
    • Transaction Management
    • Microservices Cross-cutting Concerns Options
    • Service Mesh Plus
    • Service Discovery
  • Design
    • Design Overview
    • Design First vs Code First
    • Desgin Pattern
    • Service Evolution
    • Consumer Contract and Consumer Driven Contract
    • Handling Partial Failure
    • Idempotency
    • Server Life Cycle
    • Environment Segregation
    • Database
    • Decomposition Patterns
    • Http2
    • Test Driven
    • Multi-Tenancy
    • Why check token expiration
    • WebServices to Microservices
  • Cross-Cutting Concerns
    • Concerns Overview
  • API Styles
    • Light-4j for absolute performance
    • Style Overview
    • Distributed session on IMDG
    • Hybrid Serverless Modularized Monolithic
    • Kafka - Event Sourcing and CQRS
    • REST - Representational state transfer
    • Web Server with Light
    • Websocket with Light
    • Spring Boot Integration
    • Single Page Application
    • GraphQL - A query language for your API
    • Light IBM MQ
    • Light AWS Lambda
    • Chaos Monkey
  • Infrastructure Services
    • Service Overview
    • Light Proxy
    • Light Mesh
    • Light Router
    • Light Portal
    • Messaging Infrastructure
    • Centralized Logging
    • COVID-19
    • Light OAuth2
    • Metrics and Alerts
    • Config Server
    • Tokenization
    • Light Controller
  • Tool Chain
    • Tool Chain Overview
  • Utility Library
  • Service Consumer
    • Service Consumer
  • Development
    • Development Overview
  • Deployment
    • Deployment Overview
    • Frontend Backend
    • Linux Service
    • Windows Service
    • Install Eventuate on Windows
    • Secure API
    • Client vs light-router
    • Memory Limit
    • Deploy to Kubernetes
  • Benchmark
    • Benchmark Overview
  • Tutorial
    • Tutorial Overview
  • Troubleshooting
    • Troubleshoot
  • FAQ
    • FAQ Overview
  • Milestones
  • Contribute
    • Contribute to Light
    • Development
    • Documentation
    • Example
    • Tutorial
“URL Rewrite Rule” was last updated: February 24, 2022: fixes #323 add service id url and url rewrite rule for light-router (85f7563)
Improve this page
  • News
  • Docs
  • Community
  • Reddit
  • GitHub
  • About Light
  • Getting Started
  • Architecture
  • Design
  • Cross-Cutting Concerns
  • API Styles
  • Infrastructure Services
  • Tool Chain
  • Utility Library
  • Service Consumer
  • Development
  • Deployment
  • Benchmark
  • Tutorial
  • Troubleshooting
  • FAQ
  • Milestones
  • Contribute