LogoLogo
TPI.devCommunityGithub
  • Overview
    • Introduction
      • Future Features
    • License & Disclaimer
    • APIM Architecture
      • Production Deployments and Capacity
      • Functions
      • Integration
    • Key Concepts
      • API Group
      • API Scope
      • API Client
      • End-to-End Workflow Combining API Group, API Scope, and API Client
        • Scenario: API Management for an E-commerce Platform
    • Support
    • Glossary
    • Scenarios
      • Financial Industry
        • Transforming Financial Services with digiRunner API Management
        • Redefining Financial Data Migration with digiRunner API Management Platform
      • Manufacturing Industry
        • Enabling Smart Manufacturing with Seamless API Integration and Automation via digiRunner
        • Streamlining Global Operations with API Management via digiRunner
      • Medical Industry
        • Enhancing Healthcare Data Integration and Security with digiRunner API Management
        • Revolutionizing Healthcare Interoperability with digiRunner’s Advanced API Framework
      • Insurance Industry
        • Modernizing Insurance Services with digiRunner API Management
        • Modernizing Insurance with digiRunner—Bridging Legacy Systems and Microservices
      • Government and Public Services
        • Empowering Open Government Services with digiRunner: A Mission for Integration and Transformation
        • Streamlining Public Sector Innovation via digiRunner: Driving Citizen-Centric Digital Transformation
  • Get Started
    • Installing digiRunner API Management
      • SMTP Configuration
    • Registering Your First APIs with digiRunner
    • Client Authorization and Calling APIs
    • Rate Limiting
    • Proxy Caching
    • Load Balancing
    • Sandbox Testing
    • VIP Gateway Priority Settings
    • JWE Certificate
  • Configuring IP Whitelisting via IP Binding
  • Most common use cases
    • Obtaining API Keys and Calling APIs
    • API IP Diversion
    • Viewing Real-time API Logs
    • Enabling APIs and No Auth in Batches with API Imported
    • Role-Based Access Management within a Hierarchical Structure
    • Simplified OIDC Login with Predefined Organizational Frameworks
    • Resetting User Password and Confirmation Email for Admin Console User
  • Guide
    • AC User Management
      • Users
      • My Profile
      • Roles
      • Role Mapping
      • Organization
      • Role & txID
      • Delegate AC User
      • AC OAuth 2.0 IdP
      • AC LDAP IdP
      • AC MLDAP IdP
      • AC API IdP
    • Development Mode
      • Function Management
      • Rtn Code Management
      • Embedded Function Management
    • Client Management
      • API Client
      • API Group
      • API Scope
      • Authentications
      • Security Level
      • GTW OAuth 2.0 IdP
      • GTW LDAP IdP
      • GTW API IdP
      • GTW JDBC IdP
      • Client Export/Import
    • API Management
      • API List
      • API Registry
      • API Test
      • API Modify Batch
    • Monitor & Alert
      • digiRunner Server
      • Alert Settings
    • Reports
      • API Calls
      • API RESP distribution
      • API Avg. RESP Time
      • API GTW traffic
      • Bad Attempt Report
    • Certificate Management
      • JWE Cert. List
      • JWE Cert. Management
      • TLS Cert. List
      • TLS Cert. Management
    • Application Forms
      • API Key
      • Applications
      • Approval Flow Settings
    • System Information
      • API Key Approval History
      • Scheduled Tasks
      • Recurring Tasks
      • Mail Log
    • System Configs
      • Setting
      • Items
      • Files
      • Customer Setting
      • Online Console
      • WebSocket Proxy Management
      • Static Webpage Reverse Proxy
      • RDB Connection
      • Mail Template Export/Import
  • API Integration Guide
    • Using Token for Authentication and Authorization
      • OpenID Connect (OIDC) Mode
      • Client Credentials Mode
      • Password Mode
    • Using X API Key for Authentication and Authorization
      • Applying for X API Key
      • Obtaining X API Key
      • Calling APIs Registered in digiRunner with X API Key
    • Using API Key for Authentication and Authorization
      • Applying for API Key
      • Obtaining API Key and Secret Key
      • Calculating the Signature and DGRK
      • Calling APIs Registered in digiRunner with API Key
    • Using HTTP Basic and OAuth for Authentication and Authorization
      • Calling APIs Registered in digiRunner with Basic Auth
      • Calling APIs Registered in digiRunner with No OAuth
    • Token Lifecycle Management Mechanism
      • Applying Refresh Token
      • Token Revocation
      • Token Introspection
    • JWS/JWE Integration
      • JWS Workflow
      • JWE Workflow
      • Exchanging Public Keys
      • Generating Certificate
      • Operating with JWS
      • Operating with JWE
Powered by GitBook
On this page
  • Create Static Webpage Reverse Proxy
  • Search Static Webpage Reverse Proxy
  • View Static Webpage Reverse Proxy
  • Update Static Webpage Reverse Proxy
  • Delete Static Webpage Reverse Proxy

Was this helpful?

Export as PDF
  1. Guide
  2. System Configs

Static Webpage Reverse Proxy

PreviousWebSocket Proxy ManagementNextRDB Connection

Was this helpful?

Path: System Configs >Static Webpage Reverse Proxy

Static web reverse agent is an intermediary service used to process static web resources, providing features such as requested distribution, load balancing, caching, and security to improve site performance and provide a better user experience.

Create Static Webpage Reverse Proxy

  1. Click Create to access the creation page.

  1. Fill in the data or make selections as instructed below. The fields marked with “*” are required.

  • Website Name*: An identifiable name.

  • Status*: Enable and disable the static web page reverse agent.

  • Enable Item: Multiple selections allowed, including Auth / SQL Injection / TPS / XSS / XXE / Show Log.

  • Probability*:For HA (High Availability), requests will be routed to the specified URL based on the given probability.

  • Target URL*:Specify the URL of the website.

  • TPS/Node (0 = No limit)*: The number of transactions each node can process per second.

  • Ignore API: Excluded API.

  • Target Context Path: The web context path.

  • Remark: The description of this site.

  1. Created sites can be proxied by digiRunner, with the web address being https://{{digiRunner URL}}/website/customized name/.

Search Static Webpage Reverse Proxy

Search for a static webpage reverse proxy by entering keywords.

View Static Webpage Reverse Proxy

Update Static Webpage Reverse Proxy

  1. Modify the information, and click Update to save and exit.

Delete Static Webpage Reverse Proxy

  1. A warning prompt displaying the message “Confirm Delete?” will pop up. Click Confirm to delete the Static Webpage Reverse Proxy and exit.

Search for the static web page reverse agent to view details, and click on theicon to access the Details page.

Search for the static web page reverse agent to modify, and click on the icon to access the update page.

Search for the file to delete, and click on the icon to proceed.