Kerangka pemeriksaan sistemLink to this heading#

CheckMessageLink to this heading#

class CheckMessage(level, msg, hint, obj=None, id=None)Link to this definition#

Peringatan dan kesalahan dimunculkan oleh sistem pemeriksaan harus contoh dari CheckMessage. Sebuah instance merangkum kesalahan atau peringatan dapat dilaporkan tunggal. Dia juga menyediakan konteks dan petunjuk yang berlaku pada pesan, dan penciri unik yang digunakan untuk tujuan penyaringan.

Argumen pembangun adalah:

level

Kesederhanaan dari pesan. Gunakan satu dari nilai-nilai yang sudah ditentukan: DEBUG, INFO, WARNING, ERROR, CRITICAL. Jika tingkatan lebih hebat atau sama dengan ERROR, kemudian Django akan mencegah perintah pengelolaan dari menjalankan. Pesan-pesan dengan tingkatan lebih rendah dari ERROR (yaitu peringatan) dilaporkan ke konsol, tetapi dapat disenyapkan.

msg

Deretan kalimat (kurang dari 80 karakter) pendek menggambarkan masalah. Deretan kalimat seharusnya tidak mengandung baris baru.

hint

Deretan karakter baris-tunggal menyediakan petunjuk untuk memperbaiki masalah. Jika tidak ada petunjuk disediakan, atau petunjuk adalah terbukti-sendiri dari pesan kesalahan, petunjuk dapat diabaikan, atau nilai dari None dapat digunakan.

obj

Pilihan. Sebuah obyek menyediakan konteks untuk pesan (sebagai contoh, model dimana masalah ditemukan). Obyek harus menjadi model, bidang, atau pengelola atau obyek lain apapun yang menentukan cara __str__ (pada Python 2 anda butuh menentukan cara __unicode__). Cara digunakan selagi melaporkan semua pesan dan hasilnya mendahului pesan.

id

Deretan karakter pilihan. Sebuah penciri unik untuk masalah. Penciri harus mengikuti corak applabel.X001, dimana X adalah satu dari huruf CEWID, menunjukkan kesederhanaan pesan (C for kritis, E untuk kesalahan dan sebagainya). Angka dapat dialokasikan dengan aplikasi, tetapi harus unik dalam aplikasi itu.

Ada subkelas-subkelas untuk membuat pesan dengan tingkatan umum lebih mudah. Ketika menggunakan mereka anda dapat megnabaikan argumen level karena dia disisipkan oleh nama kelas.

class Debug(msg, hint, obj=None, id=None)Link to this definition#

class Info(msg, hint, obj=None, id=None)Link to this definition#

class Warning(msg, hint, obj=None, id=None)Link to this definition#

class Error(msg, hint, obj=None, id=None)Link to this definition#

class Critical(msg, hint, obj=None, id=None)Link to this definition#

Etiket siap pakaiLink to this heading#

Sistem pemeriksaan Django diorganisasikan menggunakan etiket berikut:

• models: Checks governing model, field and manager definitions.

• signals: Periksa pada pernyataan sinyal dan penangan pendaftaran.

• admin: Periksa pernyataan situs admin apapun.

• compatibility: Masalah potensial penandaan dengan versi ditingkatkan.

• security: Periksa keamanan konfigurasi terkait.

• templates: Periksa cetakan konfigurasi terkait.

• caches: Periksa tembolok konfigurasi terkait.

• urls: Memeriksa konfigurasi URL.

Beberapa pengecekan mungkin didaftarkan dengan banyak etiket.

Pemeriksaan sistem intiLink to this heading#

AdminLink to this heading#

Admin memeriksa semua yang dilakukan sebagai bagian dari etiket admin.

Pemeriksaan berikut dilakukan pada setiap ModelAdmin (atau subkelas) yang terdaftar dengan situs admin:

• admin.E001: Nilai dari raw_id_fields harus berupa daftar atau tuple.

• admin.E002: Nilai dari raw_id_fields[n] mengacu pada <field name>, yang bukan atribut dari <model>.

• admin.E003: Nilai dari raw_id_fields[n] harus berupa ForeignKey atau ManyToManyField.

• admin.E004: Nilai-nilai dari fields harus berupa daftar atau tuple.

• admin.E005: kedua fieldsets dan fields ditentukan.

• admin.E006: Nilai dari fields mengandung bidang ganda.

• admin.E007: Nilai dari fieldsets harus berupa daftar atau tuple.

• admin.E008: Nilai dari fieldsets[n] harus berupa daftar atau tuple.

• admin.E009: Nilai dari fieldsets[n] harus panjang 2.

• admin.E010: Nilai dari fieldsets[n][1] harus berupa kamus.

• admin.E011: Nilai dari fieldsets[n][1] harus mengandung kunci fields.

• admin.E012: Ada bidang ganda dalam fieldsets[n][1].

• admin.E013: fields[n]/fieldsets[n][m] cannot include the ManyToManyField <field name>, because that field manually specifies a relationship model.

• admin.E014: The value of exclude must be a list or tuple.

• admin.E015: The value of exclude contains duplicate field(s).

• admin.E016: The value of form must inherit from BaseModelForm.

• admin.E017: The value of filter_vertical must be a list or tuple.

• admin.E018: The value of filter_horizontal must be a list or tuple.

• admin.E019: The value of filter_vertical[n]/filter_vertical[n] refers to <field name>, which is not an attribute of <model>.

• admin.E020: The value of filter_vertical[n]/filter_vertical[n] must be a ManyToManyField.

• admin.E021: The value of radio_fields must be a dictionary.

• admin.E022: The value of radio_fields refers to <field name>, which is not an attribute of <model>.

• admin.E023: The value of radio_fields refers to <field name>, which is not a ForeignKey, and does not have a choices definition.

• admin.E024: The value of radio_fields[<field name>] must be either admin.HORIZONTAL or admin.VERTICAL.

• admin.E025: The value of view_on_site must be either a callable or a boolean value.

• admin.E026: The value of prepopulated_fields must be a dictionary.

• admin.E027: The value of prepopulated_fields refers to <field name>, which is not an attribute of <model>.

• admin.E028: The value of prepopulated_fields refers to <field name>, which must not be a DateTimeField, ForeignKey or ManyToManyField.

• admin.E029: The value of prepopulated_fields[<field name>] must be a list or tuple.

• admin.E030: The value of prepopulated_fields refers to <field name>, which is not an attribute of <model>.

• admin.E031: The value of ordering must be a list or tuple.

• admin.E032: The value of ordering has the random ordering marker ?, but contains other fields as well.

• admin.E033: The value of ordering refers to <field name>, which is not an attribute of <model>.

• admin.E034: The value of readonly_fields must be a list or tuple.

• admin.E035: The value of readonly_fields[n] is not a callable, an attribute of <ModelAdmin class>, or an attribute of <model>.

AuthLink to this heading#

• auth.E001: REQUIRED_FIELDS harus berupa daftar atau rekaman.

• auth.E002: The field named as the USERNAME_FIELD for a custom user model must not be included in REQUIRED_FIELDS.

• auth.E003: <field> must be unique because it is named as the USERNAME_FIELD.

• auth.W004: <field> is named as the USERNAME_FIELD, but it is not unique.

Tipe KontenLink to this heading#

The following checks are performed when a model contains a GenericForeignKey or GenericRelation:

• contenttypes.E001: The GenericForeignKey object ID references the non-existent field <field>.

• contenttypes.E002: The GenericForeignKey content type references the non-existent field <field>.

• contenttypes.E003: <field> bukan ForeignKey.

• contenttypes.E004: <field> is not a ForeignKey to contenttypes.ContentType.

KeamananLink to this heading#

The security checks do not make your site secure. They do not audit code, do intrusion detection, or do anything particularly complex. Rather, they help perform an automated, low-hanging-fruit checklist. They help you remember the simple things that improve your site's security.

Some of these checks may not be appropriate for your particular deployment configuration. For instance, if you do your HTTP to HTTPS redirection in a load balancer, it'd be irritating to be constantly warned about not having enabled SECURE_SSL_REDIRECT. Use SILENCED_SYSTEM_CHECKS to silence unneeded checks.

The following checks are run if you use the check --deploy option:

• security.W001: You do not have django.middleware.security.SecurityMiddleware in your MIDDLEWARE_CLASSES so the SECURE_HSTS_SECONDS, SECURE_CONTENT_TYPE_NOSNIFF, SECURE_BROWSER_XSS_FILTER, and SECURE_SSL_REDIRECT settings will have no effect.

• security.W002: You do not have django.middleware.clickjacking.XFrameOptionsMiddleware in your MIDDLEWARE_CLASSES, so your pages will not be served with an 'x-frame-options' header. Unless there is a good reason for your site to be served in a frame, you should consider enabling this header to help prevent clickjacking attacks.

• security.W003: You don't appear to be using Django's built-in cross-site request forgery protection via the middleware (django.middleware.csrf.CsrfViewMiddleware is not in your MIDDLEWARE_CLASSES). Enabling the middleware is the safest approach to ensure you don't leave any holes.

• security.W004: You have not set a value for the SECURE_HSTS_SECONDS setting. If your entire site is served only over SSL, you may want to consider setting a value and enabling HTTP Strict Transport Security. Be sure to read the documentation first; enabling HSTS carelessly can cause serious, irreversible problems.

• security.W005: You have not set the SECURE_HSTS_INCLUDE_SUBDOMAINS setting to True. Without this, your site is potentially vulnerable to attack via an insecure connection to a subdomain. Only set this to True if you are certain that all subdomains of your domain should be served exclusively via SSL.

• security.W006: Your SECURE_CONTENT_TYPE_NOSNIFF setting is not set to True, so your pages will not be served with an 'x-content-type-options: nosniff' header. You should consider enabling this header to prevent the browser from identifying content types incorrectly.

• security.W007: Your SECURE_BROWSER_XSS_FILTER setting is not set to True, so your pages will not be served with an 'x-xss-protection: 1; mode=block' header. You should consider enabling this header to activate the browser's XSS filtering and help prevent XSS attacks.

• security.W008: Your SECURE_SSL_REDIRECT setting is not set to True. Unless your site should be available over both SSL and non-SSL connections, you may want to either set this setting to True or configure a load balancer or reverse-proxy server to redirect all connections to HTTPS.

• security.W009: Your SECRET_KEY has less than 50 characters or less than 5 unique characters. Please generate a long and random SECRET_KEY, otherwise many of Django's security-critical features will be vulnerable to attack.

• security.W010: You have django.contrib.sessions in your INSTALLED_APPS but you have not set SESSION_COOKIE_SECURE to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.

• security.W011: You have django.contrib.sessions.middleware.SessionMiddleware in your MIDDLEWARE_CLASSES, but you have not set SESSION_COOKIE_SECURE to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.

• security.W012: SESSION_COOKIE_SECURE is not set to True. Using a secure-only session cookie makes it more difficult for network traffic sniffers to hijack user sessions.

• security.W013: You have django.contrib.sessions in your INSTALLED_APPS, but you have not set SESSION_COOKIE_HTTPONLY to True. Using an HttpOnly session cookie makes it more difficult for cross-site scripting attacks to hijack user sessions.

• security.W014: You have django.contrib.sessions.middleware.SessionMiddleware in your MIDDLEWARE_CLASSES, but you have not set SESSION_COOKIE_HTTPONLY to True. Using an HttpOnly session cookie makes it more difficult for cross-site scripting attacks to hijack user sessions.

• security.W015: SESSION_COOKIE_HTTPONLY is not set to True. Using an HttpOnly session cookie makes it more difficult for cross-site scripting attacks to hijack user sessions.

• security.W016: CSRF_COOKIE_SECURE is not set to True. Using a secure-only CSRF cookie makes it more difficult for network traffic sniffers to steal the CSRF token.

• security.W017: CSRF_COOKIE_HTTPONLY is not set to True. Using an HttpOnly CSRF cookie makes it more difficult for cross-site scripting attacks to steal the CSRF token.

• security.W018*: Anda harus mempunyai DEBUG disetel ke True dalam menyebarkan.

• security.W019: You have django.middleware.clickjacking.XFrameOptionsMiddleware in your MIDDLEWARE_CLASSES, but X_FRAME_OPTIONS is not set to 'DENY'. The default is 'SAMEORIGIN', but unless there is a good reason for your site to serve other parts of itself in a frame, you should change it to 'DENY'.

• security.W020: ALLOWED_HOSTS harus tidak kosong dalam menyebarkan.

SitusLink to this heading#

The following checks are performed on any model using a CurrentSiteManager:

• sites.E001: CurrentSiteManager could not find a field named <field name>.

• sites.E002: CurrentSiteManager cannot use <field> as it is not a ForeignKey or ManyToManyField.

BasisdataLink to this heading#

TemplatLink to this heading#

The following checks verify that your TEMPLATES setting is correctly configured:

• templates.E001: You have 'APP_DIRS': True in your TEMPLATES but also specify 'loaders' in OPTIONS. Either remove APP_DIRS or remove the 'loaders' option.

TembolokLink to this heading#

The following checks verify that your CACHES setting is correctly configured:

• caches.E001: You must define a 'default' cache in your CACHES setting.

URLLink to this heading#

Pemeriksaan berikut dilakukan di konfigurasi URL anda:

• urls.W001: Your URL pattern <pattern> uses include() with a regex ending with a $. Remove the dollar from the regex to avoid problems including URLs.

• urls.W002: Your URL pattern <pattern> has a regex beginning with a /. Remove this slash as it is unnecessary.

• urls.W003: Your URL pattern <pattern> has a name including a :. Remove the colon, to avoid ambiguous namespace references.