diff options
author | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 19:33:14 +0000 |
---|---|---|
committer | Daniel Baumann <daniel.baumann@progress-linux.org> | 2024-04-07 19:33:14 +0000 |
commit | 36d22d82aa202bb199967e9512281e9a53db42c9 (patch) | |
tree | 105e8c98ddea1c1e4784a60a5a6410fa416be2de /netwerk/base/nsIUploadChannel.idl | |
parent | Initial commit. (diff) | |
download | firefox-esr-36d22d82aa202bb199967e9512281e9a53db42c9.tar.xz firefox-esr-36d22d82aa202bb199967e9512281e9a53db42c9.zip |
Adding upstream version 115.7.0esr.upstream/115.7.0esrupstream
Signed-off-by: Daniel Baumann <daniel.baumann@progress-linux.org>
Diffstat (limited to 'netwerk/base/nsIUploadChannel.idl')
-rw-r--r-- | netwerk/base/nsIUploadChannel.idl | 56 |
1 files changed, 56 insertions, 0 deletions
diff --git a/netwerk/base/nsIUploadChannel.idl b/netwerk/base/nsIUploadChannel.idl new file mode 100644 index 0000000000..1c059e8869 --- /dev/null +++ b/netwerk/base/nsIUploadChannel.idl @@ -0,0 +1,56 @@ +/* -*- Mode: C++; tab-width: 4; indent-tabs-mode: nil; c-basic-offset: 2 -*- */ +/* This Source Code Form is subject to the terms of the Mozilla Public + * License, v. 2.0. If a copy of the MPL was not distributed with this + * file, You can obtain one at http://mozilla.org/MPL/2.0/. */ + +#include "nsISupports.idl" + +interface nsIInputStream; + +/** + * nsIUploadChannel + * + * A channel may optionally implement this interface if it supports the + * notion of uploading a data stream. The upload stream may only be set + * prior to the invocation of asyncOpen on the channel. + */ +[scriptable, uuid(5cfe15bd-5adb-4a7f-9e55-4f5a67d15794)] +interface nsIUploadChannel : nsISupports +{ + /** + * Sets a stream to be uploaded by this channel. + * + * Most implementations of this interface require that the stream: + * (1) implement threadsafe addRef and release + * (2) implement nsIInputStream::readSegments + * (3) implement nsISeekableStream::seek + * + * History here is that we need to support both streams that already have + * headers (e.g., Content-Type and Content-Length) information prepended to + * the stream (by plugins) as well as clients (composer, uploading + * application) that want to upload data streams without any knowledge of + * protocol specifications. For this reason, we have a special meaning + * for the aContentType parameter (see below). + * + * @param aStream + * The stream to be uploaded by this channel. + * @param aContentType + * If aContentType is empty, the protocol will assume that no + * content headers are to be added to the uploaded stream and that + * any required headers are already encoded in the stream. In the + * case of HTTP, if this parameter is non-empty, then its value will + * replace any existing Content-Type header on the HTTP request. + * In the case of FTP and FILE, this parameter is ignored. + * @param aContentLength + * A value of -1 indicates that the length of the stream should be + * determined by calling the stream's |available| method. + */ + void setUploadStream(in nsIInputStream aStream, + in ACString aContentType, + in long long aContentLength); + + /** + * Get the stream (to be) uploaded by this channel. + */ + readonly attribute nsIInputStream uploadStream; +}; |