python - django rest framework: order of decorators, auth classes, dispatch to be called -


very confused order of decorators, auth classes, dispatch called in djangorestframework. seems little different django framework knowledge.

some codes:

#operation_logger: customized decorator class fileview(apiview):     parser_classes = (multipartparser,)#a     authentication_classes = (basicauthentication,)#b      @permission_classes((isauthenticated,))#c     @method_decorator(csrf_exempt)#d     @method_decorator(operation_logger)#e     def dispatch(self, request, *args, **kwargs):#f        return super(fileview, self).dispatch(request, *args, **kwargs)      @method_decorator(operation_logger)#g     def post(self, request):#h         print "xxxxpost"

what order of (a),b,c,d,e,f,g,h called when handling requests? seems b called after f before g , h?

by way, @ beginning, project traditional django project. know request should go through middlewares. now, added new app, hosts apis drf. i not sure whether request apis go through middlewares or not?

thanks

the call order specified:

  1. @method_decorator(csrf_exempt)
  2. @method_decorator(operation_logger) (#e)
  3. dispatch() calls initial() calls check_permissions() evaluates permission_classes (#b).
  4. @method_decorator(operation_logger) (#g)
  5. post()

one thing won't work, however:

@permission_classes((isauthenticated,)) on method adds permission_classes field callable (whatever is) returned (#e). doesn't work class-based views , no-op.

other parts have no fixed order, used on demand:

the authenticator called whenever needed, i.e. when user or authentication information accessed on request object.

same thing parser_classes. these passed request object , used lazily when request information accessed, e.g. request.data.


Comments

Post a Comment

Popular posts from this blog

jOOQ update returning clause with Oracle -

according http://www.jooq.org/doc/3.8/manual/sql-building/sql-statements/update-statement/ jooq doesn't support returning clause in update statements databases except firebird , postgres. does know, still correct oracle jooq? according oracle's documentation, oracle db supports returning clase delete, insert, or update statements. incorrect manual you're right - manual wrong , should fixed: https://github.com/jooq/jooq/issues/5470 single row update returning jooq 3.8 added support single row update .. returning statements. internally, uses callablestatement , pl/sql block of form: begin update "my_table" set "my_table"."column" = 'xyz' "my_table"."id" = 1 returning "my_table"."id", "my_table"."column" ?, ?; ? := sql%rowcount; end; the relevant issue is: https://github.com/jooq/jooq/issues/5190 multi row update returning a...
Read more

java - Warning equals/hashCode on @Data annotation lombok with inheritance -

i have entity inherits other. on other hand, i'm using lombok project reduce boilerplate code, put @data annotation. annotation @data inheritance produces next warning: generating equals/hashcode implementation without call superclass, though class not extend java.lang.object. if intentional, add '@equalsandhashcode(callsuper=false)' type. is advisable add annotation @equalsandhashcode (callsuper = true) or @equalsandhashcode (callsuper = false) ? if not added, 1 callsuper=false or callsuper=true ? the default value false . 1 if don't specify , ignore warning. yes, recommended add @equalsandhashcode annotation on @data annotated classes extend else object. cannot tell if need true or false , depends on class hierarchy, , need examined on case-by-case basis. however, project or package, can configure in lombok.config call super methods if not direct subclass of object. lombok.equalsandhashcode.callsuper = call for configuration system ...
Read more

java - BasicPathUsageException: Cannot join to attribute of basic type -

i using java 8 jpa (hibernate 5.2.1). have clause works perfectly, until introduce clause make use foreign key table values too. i getting following error: basicpathusageexception: cannot join attribute of basic type i think problem related fact have join table, , not sure how create join using join table. employee - employee_category - category model (employee.java): @manytomany(cascade = cascadetype.all, fetch=fetchtype.eager) @jointable ( name="employee_category", joincolumns={ @joincolumn(name="emp_id", referencedcolumnname="id") }, inversejoincolumns={ @joincolumn(name="cat_id", referencedcolumnname="id") } ) private set<category> categories; model (category.java): @id private string id; jpa when introduce following code, fails error above (i think problem new piece of code): join<t, category> category = from.join("id"); predicates.add(criteriabuilder.like(category....
Read more