proxy-route

Vivreal portal proxy routes are generated automatically using the createProxyHandler() factory pattern, handling HTTP methods, custom paths, and upstream services. This reduces manual coding by using flags to configure backend URLs, CSRF, timeout, and validation.

Yes, you can customize HTTP methods and timeout settings for an API proxy route using specific flags. The factory pattern accepts arguments for method, path, upstream path, and timeout, alongside optional CSRF and validation flags to fit your backend service requirements.

You map proxy routes to different backend services by selecting specific upstream options like cms, secure, or main. The factory pattern uses respective environment variables for these upstream URLs to direct your API traffic to the correct backend service automatically.

Yes, environment variables are required to set up an upstream API proxy. They define the backend URLs for your selected upstream services, ensuring the generated HTTP routes correctly forward requests to the intended cms, secure, or main backend endpoints.

The best way to automate proxy route generation without manual coding is using a factory pattern like createProxyHandler(). It streamlines setting up new API routes by accepting customizable arguments for methods, paths, and upstream services directly through command flags.

A limitation of using a factory pattern for HTTP proxy configuration is the dependency on predefined upstream services like cms, secure, and main. You must configure environment variables for backend URLs and apply optional flags for CSRF and validation within this fixed structure.