2.2.12.2 HTTP Header Fields Introduced by the BITS Upload Protocol

  • Article

BITS-Original-Request-URL: This specifies the destination URL of the request entity. This MUST follow the rules defined in [RFC2616] section 3.2.2. This field MUST be present.

BITS-Request-DataEntity-Name: If the back-end client and server reside on the same host, the value MAY be a local file system path, using whatever naming conventions are supported by the host. If the back-end client and server reside on different hosts, the value MUST be in Universal Naming Convention (UNC) format, accessible via the [MS-SMB] protocol. This specifies the full path to the request entity. This field MUST be present only if the notification type is NOTIFICATION_BY_REFERENCE (section 3.2.1.1), and this field MUST NOT be present otherwise. The rules specified for the Content-Name (section 2.2.1.1) header (range of characters that can be used) would apply to this as well. No limit is imposed in the back-end client on the number of characters that the value of this field could contain.<13>

BITS-Response-DataEntity-Name: This specifies the full path where the response data from the server application MUST be stored. If the back-end client and server reside on the same host, the value MAY be a local file system path, using whatever naming conventions are supported by the host. If the back-end client and server reside on different hosts, the value MUST be in UNC format, accessible via the [MS-SMB] protocol. This field MUST be present only if the notification type is NOTIFICATION_BY_REFERENCE (section 3.2.1.1), and this field MUST NOT be present otherwise. The rules specified for the Content-Name (section 2.2.1.1) header (range of characters that can be used) would apply to this as well. No limit is imposed in the back-end client on the number of characters that the value of this field could contain.<14>