 Django 4.2.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 3305 页 | 3.16 MB | 1 年前3 Django 4.2.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 3305 页 | 3.16 MB | 1 年前3
 Django 4.1.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 3240 页 | 3.13 MB | 1 年前3 Django 4.1.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 3240 页 | 3.13 MB | 1 年前3
 Django 5.1.2 Documentationdev20240916204136 into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 2923 页 | 9.62 MB | 1 年前3 Django 5.1.2 Documentationdev20240916204136 into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 2923 页 | 9.62 MB | 1 年前3
 Django 5.1.2 Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 3519 页 | 3.17 MB | 1 年前3 Django 5.1.2 Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 3519 页 | 3.17 MB | 1 年前3
 Django 4.1.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 2777 页 | 9.32 MB | 1 年前3 Django 4.1.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 2777 页 | 9.32 MB | 1 年前3
 Django 4.2.x Documentationdev20230724190741 into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 2842 页 | 9.47 MB | 1 年前3 Django 4.2.x Documentationdev20230724190741 into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: key of SECRET_KEY_FALLBACKS becomes known by an attacker. Deprecated since version 4.1: Due to the risk of remote code execution, this serializer is deprecated and will be removed in Django 5.0. Write that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen0 码力 | 2842 页 | 9.47 MB | 1 年前3
 Django 4.0.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. 156 Chapter 3. Using Django Django Documentation, Release 4.0.11.dev20230214085346 that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 2248 页 | 7.90 MB | 1 年前3 Django 4.0.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. 156 Chapter 3. Using Django Django Documentation, Release 4.0.11.dev20230214085346 that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 2248 页 | 7.90 MB | 1 年前3
 Django 3.2.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A Web application that uses GET requests for admin forms is a security risk: it can be easy for an 248 Chapter 3. Using Django Django Documentation, Release 3.2.21.dev attacker0 码力 | 2199 页 | 7.89 MB | 1 年前3 Django 3.2.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A Web application that uses GET requests for admin forms is a security risk: it can be easy for an 248 Chapter 3. Using Django Django Documentation, Release 3.2.21.dev attacker0 码力 | 2199 页 | 7.89 MB | 1 年前3
 Django 4.0.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 3184 页 | 3.14 MB | 1 年前3 Django 4.0.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 3184 页 | 3.14 MB | 1 年前3
 Django 3.2.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A Web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 3121 页 | 3.08 MB | 1 年前3 Django 3.2.x Documentationarbitrary SQL into your database. If you use string interpolation or quote the placeholder, you’re at risk for SQL injection. Executing custom SQL directly Sometimes even Manager.raw() isn’t quite enough: that can reliably get back the same thing that you put in is more fragile. For example, you run the risk of returning a datetime that was actually a string that just happened to be in the same format chosen binary data, such as an image. A Web application that uses GET requests for admin forms is a security risk: it can be easy for an attacker to mimic a form’s request to gain access to sensitive parts of the0 码力 | 3121 页 | 3.08 MB | 1 年前3
共 46 条
- 1
- 2
- 3
- 4
- 5














