• Places
    • Home
    • Graphs
    • Prefixes
  • Admin
    • Users
    • Settings
    • Plugins
    • Statistics
  • CPACK
    • Home
    • List packs
    • Submit pack
  • Repository
    • Load local file
    • Load from HTTP
    • Load from library
    • Remove triples
    • Clear repository
  • Query
    • YASGUI SPARQL Editor
    • Simple Form
    • SWISH Prolog shell
  • Help
    • Documentation
    • Tutorial
    • Roadmap
    • HTTP Services
  • Login

3.20 library(http/http_header): Handling HTTP headers
All Application Manual Name SummaryHelp

  • Documentation
    • Reference manual
    • Packages
      • SWI-Prolog HTTP support
        • The HTTP server libraries
          • library(http/http_header): Handling HTTP headers
            • http_read_request/2
            • http_read_reply_header/2
            • http_reply/2
            • http_reply/3
            • http_reply/4
            • http_reply/5
            • http_reply/6
            • http_status_reply/4
            • http_status_reply/5
            • http_status_reply/6
            • serialize_reply/2
            • http_join_headers/3
            • http_update_encoding/3
            • mime_type_encoding/2
            • http_update_connection/4
            • http_update_transfer/4
            • http_post_data/3
            • http_reply_header/3
            • http_parse_header_value/3
            • http_timestamp/2
            • http_read_header/2
            • http_parse_header/2
            • ///1
            • status_page/3
Availability::- use_module(library(http/http_header)).
Sourcehttp_update_transfer(+Request, +CGIHeader, -Transfer, -Header)
Decide on the transfer encoding from the Request and the CGI header. The behaviour depends on the setting http:chunked_transfer. If never, even explitic requests are ignored. If on_request, chunked encoding is used if requested through the CGI header and allowed by the client. If if_possible, chunked encoding is used whenever the client allows for it, which is interpreted as the client supporting HTTP 1.1 or higher.

Chunked encoding is more space efficient and allows the client to start processing partial results. The drawback is that errors lead to incomplete pages instead of a nicely formatted complete page.

ClioPatria (version V3.1.1-51-ga0b30a5)