CGI requires passing the headers from request to the environment
up until now the local Swift object metadata was exposed through regular CGI headers (like CONTENT_LENGTH or HTTPETAG)
to give way to better CGI support all these headers were renamed with prefix `LOCAL`
right now the following headers are exposed that way:
LOCALOBJECT - if exists, there is a local object present, if not - no other LOCAL* vars will be present
LOCAL_CONTENT_LENGTH - size of a file
LOCAL_CONTENT_TYPE- content type of that object
LOCAL_PATH_INFO - path to the object in the format of /account/container/obj
LOCAL_HTTP_ETAG - etag for object (md5)
LOCAL_HTTP_X_TIMESTAMP - creation timestamp
LOCAL_HTTP_CONTENT_ENCODING - content encoding, if present
LOCAL_DOCUMENT_ROOT - path to object inside the instance /dev/device
LOCAL_HTTP_X_OBJECTMETA* - user metadata headers for object
CGI requires passing the headers from request to the environment up until now the local Swift object metadata was exposed through regular CGI headers (like CONTENT_LENGTH or HTTPETAG) to give way to better CGI support all these headers were renamed with prefix `LOCAL` right now the following headers are exposed that way:
LOCALOBJECT - if exists, there is a local object present, if not - no other LOCAL* vars will be present LOCAL_CONTENT_LENGTH - size of a file LOCAL_CONTENT_TYPE- content type of that object LOCAL_PATH_INFO - path to the object in the format of
/account/container/objLOCAL_HTTP_ETAG - etag for object (md5) LOCAL_HTTP_X_TIMESTAMP - creation timestamp LOCAL_HTTP_CONTENT_ENCODING - content encoding, if present LOCAL_DOCUMENT_ROOT - path to object inside the instance/dev/deviceLOCAL_HTTP_X_OBJECTMETA* - user metadata headers for object