```
#### `QueryDict.__getitem__(key)`
Returns the last value for the given key; or an empty list (`[]`) if the
key exists but has no values. Raises
`django.utils.datastructures.MultiValueDictKeyError` if the key does not
exist. (This is a subclass of Python's standard [`KeyError`](https://docs.python.org/3/library/exceptions.html#KeyError), so you can
stick to catching `KeyError`.)
```pycon
>>> q = QueryDict("a=1&a=2&a=3", mutable=True)
>>> q.__getitem__("a")
'3'
>>> q.__setitem__("b", [])
>>> q.__getitem__("b")
[]
```
#### `QueryDict.__setitem__(key, value)`
Sets the given key to `[value]` (a list whose single element is
`value`). Note that this, as other dictionary functions that have side
effects, can only be called on a mutable `QueryDict` (such as one that
was created via [`QueryDict.copy()`](#django.http.QueryDict.copy)).
#### `QueryDict.__contains__(key)`
Mengembalikan `True` jika kunci yang diberikan disetel. Ini membuat anda melakukan, misalnya `if "foo" dalam request.GET`.
#### `QueryDict.get(key, default=None)`
Menggunakan logika sama seperti [`__getitem__()`](#django.http.QueryDict.__getitem__), dengan kaitan untuk mengembalikan nilai awalan jika kunci tidak ada.
#### `QueryDict.setdefault(key, default=None)`
Seperti [`dict.setdefault()`](https://docs.python.org/3/library/stdtypes.html#dict.setdefault), kecuai itu menggunakan [`__setitem__()`](#django.http.QueryDict.__setitem__) secara internal.
#### `QueryDict.update(other_dict)`
Takes either a `QueryDict` or a dictionary. Like [`dict.update()`](https://docs.python.org/3/library/stdtypes.html#dict.update),
except it *appends* to the current dictionary items rather than replacing
them. For example:
```pycon
>>> q = QueryDict("a=1", mutable=True)
>>> q.update({"a": "2"})
>>> q.getlist("a")
['1', '2']
>>> q["a"] # returns the last
'2'
```
#### `QueryDict.items()`
Like [`dict.items()`](https://docs.python.org/3/library/stdtypes.html#dict.items), except this uses the same last-value logic as
[`__getitem__()`](#django.http.QueryDict.__getitem__) and returns an iterator object instead of a view object.
For example:
```pycon
>>> q = QueryDict("a=1&a=2&a=3")
>>> list(q.items())
[('a', '3')]
```
#### `QueryDict.values()`
Like [`dict.values()`](https://docs.python.org/3/library/stdtypes.html#dict.values), except this uses the same last-value logic as
[`__getitem__()`](#django.http.QueryDict.__getitem__) and returns an iterator instead of a view object. For
example:
```pycon
>>> q = QueryDict("a=1&a=2&a=3")
>>> list(q.values())
['3']
```
Sebagai tambahan, `QueryDict` mempunyai metode berikut:
#### `QueryDict.copy()`
Mengembalikan salinan dari obyek menggunakan [`copy.deepcopy()`](https://docs.python.org/3/library/copy.html#copy.deepcopy). Salinan ini tidak tetap bahkan jika aslinya tidak.
#### `QueryDict.getlist(key, default=None)`
Returns a list of the data with the requested key. Returns an empty list if
the key doesn't exist and `default` is `None`. It's guaranteed to
return a list unless the default value provided isn't a list.
#### `QueryDict.setlist(key, list_)`
Mensetel kunci diberikan pada `list_` (unlike [`__setitem__()`](#django.http.QueryDict.__setitem__)).
#### `QueryDict.appendlist(key, item)`
Menambahkan sebuah barang pada daftar internal terkait dengan kunci.
#### `QueryDict.setlistdefault(key, default_list=None)`
Seperti [`setdefault()`](#django.http.QueryDict.setdefault), kecuali itu mengambil daftar dari nilai-nilai daripada nilai tunggal.
#### `QueryDict.lists()`
Like [`items()`](#django.http.QueryDict.items), except it includes all values, as a list, for each
member of the dictionary. For example:
```pycon
>>> q = QueryDict("a=1&a=2&a=3")
>>> q.lists()
[('a', ['1', '2', '3'])]
```
#### `QueryDict.pop(key)`
Returns a list of values for the given key and removes them from the
dictionary. Raises `KeyError` if the key does not exist. For example:
```pycon
>>> q = QueryDict("a=1&a=2&a=3", mutable=True)
>>> q.pop("a")
['1', '2', '3']
```
#### `QueryDict.popitem()`
Removes an arbitrary member of the dictionary (since there's no concept
of ordering), and returns a two value tuple containing the key and a list
of all values for the key. Raises `KeyError` when called on an empty
dictionary. For example:
```pycon
>>> q = QueryDict("a=1&a=2&a=3", mutable=True)
>>> q.popitem()
('a', ['1', '2', '3'])
```
#### `QueryDict.dict()`
Returns a `dict` representation of `QueryDict`. For every (key, list)
pair in `QueryDict`, `dict` will have (key, item), where item is one
element of the list, using the same logic as [`QueryDict.__getitem__()`](#django.http.QueryDict.__getitem__):
```pycon
>>> q = QueryDict("a=1&a=3&a=5")
>>> q.dict()
{'a': '5'}
```
#### `QueryDict.urlencode(safe=None)`
Returns a string of the data in query string format. For example:
```pycon
>>> q = QueryDict("a=2&b=3&b=5")
>>> q.urlencode()
'a=2&b=3&b=5'
```
Use the `safe` parameter to pass characters which don't require encoding.
For example:
```pycon
>>> q = QueryDict(mutable=True)
>>> q["next"] = "/a&b/"
>>> q.urlencode(safe="/")
'next=/a%26b/'
```
## Obyek `HttpResponse`
#### `class HttpResponse`
In contrast to [`HttpRequest`](#django.http.HttpRequest) objects, which are created automatically by
Django, [`HttpResponse`](#django.http.HttpResponse) objects are your responsibility. Each view you
write is responsible for instantiating, populating, and returning an
[`HttpResponse`](#django.http.HttpResponse).
Kelas [`HttpResponse`](#django.http.HttpResponse) berada di modul [`django.http`](#module-django.http)
### Penggunaan
#### Melewatkan string
Typical usage is to pass the contents of the page, as a string, bytestring,
or [`memoryview`](https://docs.python.org/3/library/stdtypes.html#memoryview), to the [`HttpResponse`](#django.http.HttpResponse) constructor:
```pycon
>>> from django.http import HttpResponse
>>> response = HttpResponse("Here's the text of the web page.")
>>> response = HttpResponse("Text only, please.", content_type="text/plain")
>>> response = HttpResponse(b"Bytestrings are also accepted.")
>>> response = HttpResponse(memoryview(b"Memoryview as well."))
```
But if you want to add content incrementally, you can use `response` as a
file-like object:
```pycon
>>> response = HttpResponse()
>>> response.write("Here's the text of the web page.
")
>>> response.write("Here's another paragraph.
")
```
#### Melewatkan perulangan
Finally, you can pass `HttpResponse` an iterator rather than strings.
`HttpResponse` will consume the iterator immediately, store its content as a
string, and discard it. Objects with a `close()` method such as files and
generators are immediately closed.
If you need the response to be streamed from the iterator to the client, you
must use the [`StreamingHttpResponse`](#django.http.StreamingHttpResponse) class instead.
#### Mengatur bidang kepala
To set or remove a header field in your response, use
[`HttpResponse.headers`](#django.http.HttpResponse.headers):
```pycon
>>> response = HttpResponse()
>>> response.headers["Age"] = 120
>>> del response.headers["Age"]
```
You can also manipulate headers by treating your response like a dictionary:
```pycon
>>> response = HttpResponse()
>>> response["Age"] = 120
>>> del response["Age"]
```
This proxies to `HttpResponse.headers`, and is the original interface offered
by `HttpResponse`.
When using this interface, unlike a dictionary, `del` doesn't raise
`KeyError` if the header field doesn't exist.
You can also set headers on instantiation:
```pycon
>>> response = HttpResponse(headers={"Age": 120})
```
For setting the `Cache-Control` and `Vary` header fields, it is recommended
to use the [`patch_cache_control()`](/id/5.2/ref/utils/#django.utils.cache.patch_cache_control) and
[`patch_vary_headers()`](/id/5.2/ref/utils/#django.utils.cache.patch_vary_headers) methods from
[`django.utils.cache`](/id/5.2/ref/utils/#module-django.utils.cache), since these fields can have multiple, comma-separated
values. The "patch" methods ensure that other values, e.g. added by a
middleware, are not removed.
HTTP header fields cannot contain newlines. An attempt to set a header field
containing a newline character (CR or LF) will raise `BadHeaderError`
#### memberitahu peramban untuk memperlakukan tanggapan sebagai sebuah berkas lampiran
To tell the browser to treat the response as a file attachment, set the
`Content-Type` and `Content-Disposition` headers. For example, this is how
you might return a Microsoft Excel spreadsheet:
```pycon
>>> response = HttpResponse(
... my_data,
... headers={
... "Content-Type": "application/vnd.ms-excel",
... "Content-Disposition": 'attachment; filename="foo.xls"',
... },
... )
```
There's nothing Django-specific about the `Content-Disposition` header, but
it's easy to forget the syntax, so we've included it here.
### Atribut
#### `HttpResponse.content`
Sebuah bytestring mewakili isi, disandikan dari string jika dibutuhkan.
#### `HttpResponse.text`
> **New in Django 5.2**
A string representation of [`HttpResponse.content`](#django.http.HttpResponse.content), decoded using the
response's [`HttpResponse.charset`](#django.http.HttpResponse.charset) (defaulting to `UTF-8` if empty).
#### `HttpResponse.cookies`
A [`http.cookies.SimpleCookie`](https://docs.python.org/3/library/http.cookies.html#http.cookies.SimpleCookie) object holding the cookies included
in the response.
#### `HttpResponse.headers`
A case insensitive, dict-like object that provides an interface to all
HTTP headers on the response, except a `Set-Cookie` header. See
[Mengatur bidang kepala](#setting-header-fields) and [`HttpResponse.cookies`](#django.http.HttpResponse.cookies).
#### `HttpResponse.charset`
A string denoting the charset in which the response will be encoded. If not
given at `HttpResponse` instantiation time, it will be extracted from
`content_type` and if that is unsuccessful, the
[`DEFAULT_CHARSET`](/id/5.2/ref/settings/#std-setting-DEFAULT_CHARSET) setting will be used.
#### `HttpResponse.status_code`
The [**HTTP status code**](https://datatracker.ietf.org/doc/html/rfc9110.html#section-15) for the response.
Unless [`reason_phrase`](#django.http.HttpResponse.reason_phrase) is explicitly set, modifying the value of
`status_code` outside the constructor will also modify the value of
`reason_phrase`.
#### `HttpResponse.reason_phrase`
The HTTP reason phrase for the response. It uses the [**HTTP standard's**](https://datatracker.ietf.org/doc/html/rfc9110.html#section-15.1) default reason phrases.
Meskipun secara tegas mensetel, `reason_phrase` ditentukan oleh nilai [`status_code`](#django.http.HttpResponse.status_code).
#### `HttpResponse.streaming`
Ini selalu `False`.
Atribut ini ada sehingga middleware dapat memperlakukan aliran tanggapan berbeda dari tanggapan biasanya.
#### `HttpResponse.closed`
`True` jika tanggapan telah ditutup.
### Cara
#### `HttpResponse.__init__(content=b'', content_type=None, status=200, reason=None, charset=None, headers=None)`
Instantiates an `HttpResponse` object with the given page content,
content type, and headers.
`content` is most commonly an iterator, bytestring, [`memoryview`](https://docs.python.org/3/library/stdtypes.html#memoryview),
or string. Other types will be converted to a bytestring by encoding their
string representation. Iterators should return strings or bytestrings and
those will be joined together to form the content of the response.
`content_type` is the MIME type optionally completed by a character set
encoding and is used to fill the HTTP `Content-Type` header. If not
specified, it is formed by `'text/html'` and the
[`DEFAULT_CHARSET`](/id/5.2/ref/settings/#std-setting-DEFAULT_CHARSET) settings, by default:
`"text/html; charset=utf-8"`.
`status` is the [**HTTP status code**](https://datatracker.ietf.org/doc/html/rfc9110.html#section-15) for the
response. You can use Python's [`http.HTTPStatus`](https://docs.python.org/3/library/http.html#http.HTTPStatus) for meaningful
aliases, such as `HTTPStatus.NO_CONTENT`.
`reason` adalah ungkapan tanggapan HTTP. Jika tidak disediakan, ungkapan awalan akan digunakan.
`charset` is the charset in which the response will be encoded. If not
given it will be extracted from `content_type`, and if that
is unsuccessful, the [`DEFAULT_CHARSET`](/id/5.2/ref/settings/#std-setting-DEFAULT_CHARSET) setting will be used.
`headers` is a [`dict`](https://docs.python.org/3/library/stdtypes.html#dict) of HTTP headers for the response.
#### `HttpResponse.__setitem__(header, value)`
Setel nama kepala diberikan pada nilai diberikan. Kedua `header` dan `value` harus berupa string.
#### `HttpResponse.__delitem__(header)`
Hapus kepala dengan nama diberikan. Gagal diam jika kepala tidak ada. kasus-tidak-peka.
#### `HttpResponse.__getitem__(header)`
Mengembalikan nilai untk nama kepala diberikan. Kasus-tidak-peka.
#### `HttpResponse.get(header, alternate=None)`
Returns the value for the given header, or an `alternate` if the header
doesn't exist.
#### `HttpResponse.has_header(header)`
Mengembalikan `True` atau `False` berdasarkan pada pemeriksaan kasus-tidak-peka untuk kepala dengan nama diberikan.
#### `HttpResponse.items()`
Acts like [`dict.items()`](https://docs.python.org/3/library/stdtypes.html#dict.items) for HTTP headers on the response.
#### `HttpResponse.setdefault(header, value)`
Setel sebuah kepala meskipun itu sudah dikirim.
#### `HttpResponse.set_cookie(key, value='', max_age=None, expires=None, path='/', domain=None, secure=False, httponly=False, samesite=None)`
Setel sebuah kue. Parameter sama seperti dalam obyek kue [`Morsel`](https://docs.python.org/3/library/http.cookies.html#http.cookies.Morsel) dalam pustaka standar Python.
- `max_age` should be a [`timedelta`](https://docs.python.org/3/library/datetime.html#datetime.timedelta) object, an integer
number of seconds, or `None` (default) if the cookie should last only
as long as the client's browser session. If `expires` is not specified,
it will be calculated.
- `expires` harus salah satu berupa string dalam bentuk `"Wdy, DD-Mon-YY HH:MM:SS GMT"` atau obyek `datetime.datetime` dalam UTC. Jika `expires` adalah obyek `datetime`, `max_age` akan dihitung.
- Gunakan\`\`domain\`\` jika anda ingi mensetel kue lintas-ranah. Sebagai contoh, `domain="example.com"` akan mensetel sebuah kue yang dapat dibaca oleh ranah www.example.com, blog.example.com, dll. Sebaliknya, sebuah kue akan hanya dapat dibaca oleh ranah yang mensetel nya.
- Use `secure=True` if you want the cookie to be only sent to the server
when a request is made with the `https` scheme.
- Gunakan `httponly=True` jika anda ingin mencegah javaScript sisi-klien dari memiliki akses ke kue.
[HttpOnly](https://owasp.org/www-community/HttpOnly) is a flag included in a Set-Cookie HTTP response header. It's
part of the [**RFC 6265**](https://datatracker.ietf.org/doc/html/rfc6265.html#section-4.1.2.6) standard for cookies
and can be a useful way to mitigate the risk of a client-side script
accessing the protected cookie data.
- Use `samesite='Strict'` or `samesite='Lax'` to tell the browser not
to send this cookie when performing a cross-origin request. [SameSite](https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Set-Cookie#samesitesamesite-value)
isn't supported by all browsers, so it's not a replacement for Django's
CSRF protection, but rather a defense in depth measure.
Use `samesite='None'` (string) to explicitly state that this cookie is
sent with all same-site and cross-site requests.
> **Warning**
>
> [**RFC 6265**](https://datatracker.ietf.org/doc/html/rfc6265.html#section-6.1) states that user agents should
> support cookies of at least 4096 bytes. For many browsers this is also
> the maximum size. Django will not raise an exception if there's an
> attempt to store a cookie of more than 4096 bytes, but many browsers
> will not set the cookie correctly.
#### `HttpResponse.set_signed_cookie(key, value, salt='', max_age=None, expires=None, path='/', domain=None, secure=False, httponly=False, samesite=None)`
Like [`set_cookie()`](#django.http.HttpResponse.set_cookie), but
[cryptographic signing](/id/5.2/topics/signing/) the cookie before setting
it. Use in conjunction with [`HttpRequest.get_signed_cookie()`](#django.http.HttpRequest.get_signed_cookie).
You can use the optional `salt` argument to put the cookie into a
separate signature namespace, but you will need to remember to pass it to
the corresponding
[`HttpRequest.get_signed_cookie()`](#django.http.HttpRequest.get_signed_cookie) call.
#### `HttpResponse.delete_cookie(key, path='/', domain=None, samesite=None)`
Menghapus kue dengan kunci yang diberikan. Gagal secara diam jika kunci tidak ada.
Dikarenakan cara kue bekerja, `path` dan `domain` harus berupa nilai sama anda gunakan dalam `set_cookie()` -- sebaliknya kue mungkin tidak dihapus.
#### `HttpResponse.close()`
This method is called at the end of the request directly by the WSGI
server.
#### `HttpResponse.write(content)`
Metode ini membuat sebuah instance [`HttpResponse`](#django.http.HttpResponse) sebuah obyek seperti-berkas.
#### `HttpResponse.flush()`
Metode ini membuat sebuah instance [`HttpResponse`](#django.http.HttpResponse) sebuah obyek seperti-berkas.
#### `HttpResponse.tell()`
Metode ini membuat sebuah instance [`HttpResponse`](#django.http.HttpResponse) sebuah obyek seperti-berkas.
#### `HttpResponse.getvalue()`
Mengembalikan nilai dari [`HttpResponse.content`](#django.http.HttpResponse.content). Metode ini membuat sebuah instance [`HttpResponse`](#django.http.HttpResponse) sebuah obyek seperti-aliran.
#### `HttpResponse.readable()`
Selalu `False`. Metode ini membuat sebuah instance [`HttpResponse`](#django.http.HttpResponse) obyek seperti-aliran.
#### `HttpResponse.seekable()`
Selalu `False`. Metode ini membuat sebuah instance [`HttpResponse`](#django.http.HttpResponse) obyek seperti-aliran.
#### `HttpResponse.writable()`
Selalu `True`. Metode ini membuat sebuah instance [`HttpResponse`](#django.http.HttpResponse) obyek seperti-aliran.
#### `HttpResponse.writelines(lines)`
Tulis sebuah baris pada tanggapan. Pemisah baris tidak ditambahkan. Metode ini membuat sebuah contoh [`HttpResponse`](#django.http.HttpResponse) sebuah obyek seperti-aliran.
### Subkelas `HttpResponse`
Django menyertakan sebuah angka dari subkelas-subkelas `HttpResponse` yang menangani jenis-jenis berbeda dari tanggapan HTTP. Seperti `HttpResponse`, subkelas-subkelas ini tinggal dalam [`django.http`](#module-django.http).
#### `class HttpResponseRedirect`
The first argument to the constructor is required -- the path to redirect
to. This can be a fully qualified URL
(e.g. `'https://www.yahoo.com/search/'`), an absolute path with no domain
(e.g. `'/search/'`), or even a relative path (e.g. `'search/'`). In that
last case, the client browser will reconstruct the full URL itself
according to the current path.
The constructor accepts an optional `preserve_request` keyword argument
that defaults to `False`, producing a response with a 302 status code. If
`preserve_request` is `True`, the status code will be 307 instead.
See [`HttpResponse`](#django.http.HttpResponse) for other optional constructor arguments.
#### `url`
Ini atribut hanya-baca mewakili tanggapan URL akan mengalihkan ke (setara pada kepala tanggapan `Location`).
> **Changed in Django 5.2**
>
> The `preserve_request` argument was added.
#### `class HttpResponsePermanentRedirect`
Like [`HttpResponseRedirect`](#django.http.HttpResponseRedirect), but it returns a permanent redirect
(HTTP status code 301) instead of a "found" redirect (status code 302).
When `preserve_request=True`, the response's status code is 308.
> **Changed in Django 5.2**
>
> The `preserve_request` argument was added.
#### `class HttpResponseNotModified`
Pembangun tidak mengambil argumen apapun dan tidak ada isi harus ditambahkan pada tanggapan ini. Gunakan ini untuk merancang bahwa sebuah halaman belum dirubah sejak permintaan terakhir pengguna (kode keadaan 304).
#### `class HttpResponseBadRequest`
Bertindak seperti [`HttpResponse`](#django.http.HttpResponse) tetapi menggunakan kode keadaan 400.
#### `class HttpResponseNotFound`
Bertindak seperti [`HttpResponse`](#django.http.HttpResponse) tetapi menggunakan kode keadaan 404.
#### `class HttpResponseForbidden`
Bertindak seperti [`HttpResponse`](#django.http.HttpResponse) tetapi menggunakan kode keadaan 403.
#### `class HttpResponseNotAllowed`
Seperti [`HttpResponse`](#django.http.HttpResponse), tetapi menggunakan kode keadaan 405. Argumen pertama pada pembangun adalah dibutuhkan: sebuah daftar metode-metode diizinkan (misalnya `['GET', 'POST']`).
#### `class HttpResponseGone`
Bertindak seperti [`HttpResponse`](#django.http.HttpResponse) tetapi menggunakan kode keadaan 410.
#### `class HttpResponseServerError`
Bertindak seperti [`HttpResponse`](#django.http.HttpResponse) tetapi menggunakan kode keadaan 500.
> **Note**
>
> If a custom subclass of [`HttpResponse`](#django.http.HttpResponse) implements a `render`
> method, Django will treat it as emulating a
> [`SimpleTemplateResponse`](/id/5.2/ref/template-response/#django.template.response.SimpleTemplateResponse), and the
> `render` method must itself return a valid response object.
#### Custom response classes
If you find yourself needing a response class that Django doesn't provide, you
can create it with the help of [`http.HTTPStatus`](https://docs.python.org/3/library/http.html#http.HTTPStatus). For example:
```
from http import HTTPStatus
from django.http import HttpResponse
class HttpResponseNoContent(HttpResponse):
status_code = HTTPStatus.NO_CONTENT
```
## Obyek `JsonResponse`
#### `class JsonResponse(data, encoder=DjangoJSONEncoder, safe=True, json_dumps_params=None, **kwargs)`
An [`HttpResponse`](#django.http.HttpResponse) subclass that helps to create a JSON-encoded
response. It inherits most behavior from its superclass with a couple
differences:
Its default `Content-Type` header is set to `application/json`.
Parameter pertama, `data`, harus berupa sebuah contoh `dict`. Jika parameter `safe` disetel menjadi `False` (lihat dibawah) itu dapat berupa obyek JSON-dapat-diserialisasi apapun.
`encoder`, yang awalan pada [`django.core.serializers.json.DjangoJSONEncoder`](/id/5.2/topics/serialization/#django.core.serializers.json.DjangoJSONEncoder), akan digunakan untuk menserialkan data. Lihat [JSON serialization](/id/5.2/topics/serialization/#serialization-formats-json) untuk rincian lebih tentang penserial ini.
Parameter boolean `safe` awalan pada `True`. Jika itu disetel menjadi `False`, obyek apapun dapat dilewatkan untuk serialisasi (sebaliknya hanya contoh `dict` diizinkan). Jika `safe` adalah `True` dan obyek bukan-`dict` dilewatkan sebagai argumen pertama, sebuah [`TypeError`](https://docs.python.org/3/library/exceptions.html#TypeError) akan dimunculkan.
Parameter `json_dumps_params` adalah sebuah dictionary dari argumen kata kunci untuk dilewatkan ke panggilan `json.dumps()` digunakan untuk membangkitkan tanggapan.
### Penggunaan
Typical usage could look like:
```pycon
>>> from django.http import JsonResponse
>>> response = JsonResponse({"foo": "bar"})
>>> response.content
b'{"foo": "bar"}'
```
#### Menserialkan obyek bukan-dictionary
In order to serialize objects other than `dict` you must set the `safe`
parameter to `False`:
```pycon
>>> response = JsonResponse([1, 2, 3], safe=False)
```
Tanpa melewatkan `safe=False`, sebuah [`TypeError`](https://docs.python.org/3/library/exceptions.html#TypeError) akan dimunculkan.
Note that an API based on `dict` objects is more extensible, flexible, and
makes it easier to maintain forwards compatibility. Therefore, you should avoid
using non-dict objects in JSON-encoded response.
> **Warning**
>
> Before the [5th edition of ECMAScript](https://262.ecma-international.org/5.1/#sec-11.1.4) it was possible to
> poison the JavaScript `Array` constructor. For this reason, Django does
> not allow passing non-dict objects to the
> [`JsonResponse`](#django.http.JsonResponse) constructor by default. However, most
> modern browsers implement ECMAScript 5 which removes this attack vector.
> Therefore it is possible to disable this security precaution.
#### Merubah penyandi JSON awalan
If you need to use a different JSON encoder class you can pass the `encoder`
parameter to the constructor method:
```pycon
>>> response = JsonResponse(data, encoder=MyJSONEncoder)
```
## Obyek `StreamingHttpResponse`
#### `class StreamingHttpResponse`
The [`StreamingHttpResponse`](#django.http.StreamingHttpResponse) class is used to stream a response from
Django to the browser.
> **Advanced usage**
>
> [`StreamingHttpResponse`](#django.http.StreamingHttpResponse) is somewhat advanced, in that it is
> important to know whether you'll be serving your application synchronously
> under WSGI or asynchronously under ASGI, and adjust your usage
> appropriately.
>
> Please read these notes with care.
An example usage of [`StreamingHttpResponse`](#django.http.StreamingHttpResponse) under WSGI is streaming
content when generating the response would take too long or uses too much
memory. For instance, it's useful for [generating large CSV files](/id/5.2/howto/outputting-csv/#streaming-csv-files).
There are performance considerations when doing this, though. Django, under
WSGI, is designed for short-lived requests. Streaming responses will tie a
worker process for the entire duration of the response. This may result in poor
performance.
Generally speaking, you would perform expensive tasks outside of the
request-response cycle, rather than resorting to a streamed response.
When serving under ASGI, however, a [`StreamingHttpResponse`](#django.http.StreamingHttpResponse) need not
stop other requests from being served whilst waiting for I/O. This opens up
the possibility of long-lived requests for streaming content and implementing
patterns such as long-polling, and server-sent events.
Even under ASGI note, [`StreamingHttpResponse`](#django.http.StreamingHttpResponse) should only be used in
situations where it is absolutely required that the whole content isn't
iterated before transferring the data to the client. Because the content can't
be accessed, many middleware can't function normally. For example the `ETag`
and `Content-Length` headers can't be generated for streaming responses.
The [`StreamingHttpResponse`](#django.http.StreamingHttpResponse) is not a subclass of [`HttpResponse`](#django.http.HttpResponse),
because it features a slightly different API. However, it is almost identical,
with the following notable differences:
- It should be given an iterator that yields bytestrings, [`memoryview`](https://docs.python.org/3/library/stdtypes.html#memoryview),
or strings as content. When serving under WSGI, this should be a sync
iterator. When serving under ASGI, then it should be an async iterator.
- You cannot access its content, except by iterating the response object
itself. This should only occur when the response is returned to the client:
you should not iterate the response yourself.
Under WSGI the response will be iterated synchronously. Under ASGI the
response will be iterated asynchronously. (This is why the iterator type must
match the protocol you're using.)
To avoid a crash, an incorrect iterator type will be mapped to the correct
type during iteration, and a warning will be raised, but in order to do this
the iterator must be fully-consumed, which defeats the purpose of using a
[`StreamingHttpResponse`](#django.http.StreamingHttpResponse) at all.
- It has no `content` attribute. Instead, it has a
[`streaming_content`](#django.http.StreamingHttpResponse.streaming_content) attribute. This can be used
in middleware to wrap the response iterable, but should not be consumed.
- It has no `text` attribute, as it would require iterating the response
object.
- Anda tidak dapat menggunakan obyek seperti-berkas metode `tell()` atau `write()`. Melakukan itu akan memunculkan sebuah pengecualian.
The [`HttpResponseBase`](#django.http.HttpResponseBase) base class is common between
[`HttpResponse`](#django.http.HttpResponse) and [`StreamingHttpResponse`](#django.http.StreamingHttpResponse).
### Atribut
#### `StreamingHttpResponse.streaming_content`
An iterator of the response content, bytestring encoded according to
[`HttpResponse.charset`](#django.http.HttpResponse.charset).
#### `StreamingHttpResponse.status_code`
The [**HTTP status code**](https://datatracker.ietf.org/doc/html/rfc9110.html#section-15) for the response.
Unless [`reason_phrase`](#django.http.StreamingHttpResponse.reason_phrase) is explicitly set, modifying the value of
`status_code` outside the constructor will also modify the value of
`reason_phrase`.
#### `StreamingHttpResponse.reason_phrase`
The HTTP reason phrase for the response. It uses the [**HTTP standard's**](https://datatracker.ietf.org/doc/html/rfc9110.html#section-15.1) default reason phrases.
Meskipun secara tegas mensetel, `reason_phrase` ditentukan oleh nilai [`status_code`](#django.http.StreamingHttpResponse.status_code).
#### `StreamingHttpResponse.streaming`
Ini selalu `True`.
#### `StreamingHttpResponse.is_async`
Boolean indicating whether [`StreamingHttpResponse.streaming_content`](#django.http.StreamingHttpResponse.streaming_content)
is an asynchronous iterator or not.
This is useful for middleware needing to wrap
[`StreamingHttpResponse.streaming_content`](#django.http.StreamingHttpResponse.streaming_content).
### Handling disconnects
If the client disconnects during a streaming response, Django will cancel the
coroutine that is handling the response. If you want to clean up resources
manually, you can do so by catching the `asyncio.CancelledError`:
```
async def streaming_response():
try:
# Do some work here
async for chunk in my_streaming_iterator():
yield chunk
except asyncio.CancelledError:
# Handle disconnect
...
raise
async def my_streaming_view(request):
return StreamingHttpResponse(streaming_response())
```
This example only shows how to handle client disconnection while the response
is streaming. If you perform long-running operations in your view before
returning the `StreamingHttpResponse` object, then you may also want to
[handle disconnections in the view](/id/5.2/topics/async/#async-handling-disconnect) itself.
## Obyek `FileResponse`
#### `class FileResponse(open_file, as_attachment=False, filename='', **kwargs)`
[`FileResponse`](#django.http.FileResponse) is a subclass of [`StreamingHttpResponse`](#django.http.StreamingHttpResponse)
optimized for binary files. It uses [**wsgi.file\_wrapper**](https://peps.python.org/pep-3333/#optional-platform-specific-file-handling) if provided by the wsgi
server, otherwise it streams the file out in small chunks.
If `as_attachment=True`, the `Content-Disposition` header is set to
`attachment`, which asks the browser to offer the file to the user as a
download. Otherwise, a `Content-Disposition` header with a value of
`inline` (the browser default) will be set only if a filename is
available.
If `open_file` doesn't have a name or if the name of `open_file` isn't
appropriate, provide a custom file name using the `filename` parameter.
Note that if you pass a file-like object like `io.BytesIO`, it's your
task to `seek()` it before passing it to `FileResponse`.
The `Content-Length` header is automatically set when it can be guessed
from the content of `open_file`.
The `Content-Type` header is automatically set when it can be guessed
from the `filename`, or the name of `open_file`.
`FileResponse` accepts any file-like object with binary content, for example
a file open in binary mode like so:
```pycon
>>> from django.http import FileResponse
>>> response = FileResponse(open("myfile.png", "rb"))
```
Berkas akan ditutup otomatis, jadi jangan membuka itu dengan pengelola konteks.
> **Use under ASGI**
>
> Python's file API is synchronous. This means that the file must be fully
> consumed in order to be served under ASGI.
>
> In order to stream a file asynchronously you need to use a third-party
> package that provides an asynchronous file API, such as [aiofiles](https://github.com/Tinche/aiofiles).
### Cara
#### `FileResponse.set_headers(open_file)`
This method is automatically called during the response initialization and
set various headers (`Content-Length`, `Content-Type`, and
`Content-Disposition`) depending on `open_file`.
## `HttpResponseBase` class
#### `class HttpResponseBase`
The [`HttpResponseBase`](#django.http.HttpResponseBase) class is common to all Django responses.
It should not be used to create responses directly, but it can be
useful for type-checking.