FLAT
CouperSevenval TechnologiesDocker ImageGithub
master
master
  • Changelog
  • FLAT
  • Administration
    • Configuration
    • Docker
    • Logging
  • Cookbook
    • Using the Built-in Mocking
    • Performing Additional Checks on JWT Access Tokens
    • Logging Custom Fields
    • Using Environment Variables
    • Handling Errors with an Error Flow
    • File Serving
    • Forwarding a Request to an Upstream API
    • Extracting Common Initialization Flow Tasks
    • Encoding and Decoding JWT
    • Passing Header Fields to the Client
    • How can I pass an arbitrary header field to an upstream system?
    • Performing Additional Checks on JWT Access Tokens
    • Proxying requests to Upstream APIs
    • Increasing the Request Timeout
    • How can I see what the client requested?
    • Using Swagger UI for API Documentation
    • Testing API Requests
    • Testing with Backend Requests
    • Testing Templates
    • Sending POST Requests
    • Processing Upstream Responses
    • Protecting Access using JWT Tokens
  • Reference
    • Configuration
    • Debugging
    • flat CLI
    • Flow
    • Variables
    • OpenAPI / Swagger Integration
    • OpenAPI
      • CORS - Cross-Origin Resource Sharing
    • OpenAPI
      • Differences from Swagger
    • OpenAPI
      • Mocking
    • OpenAPI
      • Routing
    • OpenAPI
      • Security
    • OpenAPI
      • Upstream APIs
    • OpenAPI
      • Validation
    • Flow Actions
      • assert Action
      • auth Action
      • backend-flow Action
      • copy Action
      • debug Action
      • dump Action
      • echo Action
      • error Action
      • eval Action
      • log Action
      • nameshave Action
      • pass-body Action
      • proxy-request Action
      • regex Action
      • request Action
      • requests Action
      • serve Action
      • set-config Action
      • set-env Action
      • set-response-headers Action
      • set-status Action
      • sub-flow Action
      • template Action
      • test-request Action
      • xslt Action
    • Functions
      • apply-codecs()
      • array-reverse()
      • array()
      • base64-decode()
      • base64-encode()
      • body()
      • calc-signature()
      • capitalize-first()
      • content()
      • decrypt-xml()
      • decrypt()
      • encrypt()
      • ends-with()
      • file-exists()
      • fit-document()
      • fit-log()
      • fit-serialize()
      • get-log()
      • has-class()
      • html-parse()
      • join()
      • json-doc()
      • json-parse()
      • json-stringify()
      • json-to-csv()
      • json-to-xml()
      • jwt-decode()
      • jwt-encode()
      • ldap-lookup()
      • ldap-query()
      • lookup()
      • matches()
      • md5()
      • replace()
      • sort()
      • split()
      • tolower()
      • toupper()
      • trim()
      • unixtime()
      • urldecode(), url-decode()
      • urlencode(), url-encode()
      • uuid3() and uuid4()
      • verify-signature()
      • verify-xmldsig()
      • xml-parse()
      • xml-to-json()
    • Templating
      • {{,}}
      • Comment {{// …}}
      • Dot {{.}}
      • Conditional `{{if <condition>}} … {{elseif <condition> }} … {{else}} … {{end}}
      • loop
      • ?? Operator
      • Object XML Notation (OXN)
      • Pair Producer {{: …}}
      • Placeholder
      • Template Variables
      • with
    • Testing
  • Tutorial
Powered by GitBook
On this page
  • Syntax
  • Usage
  • Errors
  • See also

Was this helpful?

  1. Reference
  2. Flow Actions

serve Action

The serve action can be used to deliver local files to clients. The action implements a simple file server. Optionally, processing of the flow can continue if the content provided by the serve action needs to be modified.

Syntax

dir and fallback-doc are mandatory:

  • dir="…" defines the directory from which the local files are read. That directory must exist within the project path. The dir directory is resolved relative to the calling flow file.

  • fallback-doc: Defines a fallback document. This document will be used if the requested file cannot be found. The fallback-doc file is resolved relative to the calling flow file.

  • terminate="true|false": if true (default) the file loaded by serve is sent to the client and flow processing stops. Otherwise, the flow continues.

  • The action has no input (in).

  • If further processing of the loaded file is required, the output of serve can be redirected via the out attribute.

<flow>
  …
  <serve dir="../htdocs" fallback-doc="/index.html"/>
  …
</flow>

Usage

The $request/path is resolved relative to dir. If the resolved path references a directory instead of a file, index.html within that directory is used instead. If $request/path references a directory but does not end with a slash (/), a 301 Moved Permanently redirection to the same path with a trailing slash (/) is executed.

If the requested file is found, the following HTTP header fields are set:

  • Content-Type

  • Content-Length

  • Last-Modified

The Content-Type is determined by the suffix of the file. The HTTP status code is set to 200 OK.

If the file is not readable, the HTTP status is set to 403 Forbidden.

Errors

  • The attribute dir is missing.

  • The attribute fallback-doc is missing.

  • The directory referenced by dir does not exist or cannot be read.

  • The directory referenced by dir is not within the project directory.

  • The file referenced by fallback-doc is to be loaded but does not exist or cannot be read.

See also

Previousrequests ActionNextset-config Action

Last updated 5 years ago

Was this helpful?

(cookbook)

File Serving
Default Flow