The most difficult part is that you have to consider both directions at the same time when setting the order. I would say that’s a flaw in the design and I personally would opt for a separate request and response middleware order (so you wouldn’t need hacks like FetchFromCacheMiddleware and UpdateCacheMiddleware). But… alas, it’s this … Read more
I’ve just recently hit this problem. This solution doesn’t use the Django Rest Framework Response, but if your server just returns JSON this solution might work for you. New in django 1.7 or greater is the JSONResponse response type. https://docs.djangoproject.com/en/3.0/ref/request-response/#jsonresponse-objects In the middleware you can return these responses without having all the “No accepted renderers” … Read more
Sometimes if you see “OperationalError: (2006, ‘MySQL server has gone away’)”, it is because you are issuing a query that is too large. This can happen, for instance, if you’re storing your sessions in MySQL, and you’re trying to put something really big in the session. To fix the problem, you need to increase the … Read more
Rather than changing the template directories dynamically you could modify the request and add a value that lets your view know if the user is on an iphone or not. Then wrap render_to_response (or whatever you are using for creating HttpResponse objects) to grab the iphone version of the template instead of the standard html … Read more
The method I am going for at the moment uses a subclass of HttpResponse: from django.template import loader from django.http import HttpResponse # use custom response class to override HttpResponse.close() class LogSuccessResponse(HttpResponse): def close(self): super(LogSuccessResponse, self).close() # do whatever you want, this is the last codepoint in request handling if self.status_code == 200: print(‘HttpResponse successful: … Read more
You want decorator_from_middleware. from django.utils.decorators import decorator_from_middleware @decorator_from_middleware(MyMiddleware) def view_function(request): #blah blah It doesn’t apply to URLs, but it works per-view, so you can have fine-grained control over its effect.
Write middleware that does this in __init__ and afterwards raise django.core.exceptions.MiddlewareNotUsed from the __init__, django will remove it for all requests :). __init__ is called at startup by the way, not at the first request, so it won’t block your first user. There is talk about adding a startup signal, but that won’t be available … Read more
Since you are using the new MIDDLEWARE settings, your Middleware class must accept a get_response argument: https://docs.djangoproject.com/en/1.10/topics/http/middleware/#writing-your-own-middleware You could write your class like this: from django.http import HttpResponse class ExceptionMiddleware(object): def __init__(self, get_response): self.get_response = get_response def __call__(self, request): return self.get_response(request) def process_exception(self, request, exception): return HttpResponse(“in exception”) You could also use the MiddlewareMixin to … Read more
First: The path structure If you don’t have it you need to create the middleware folder within your app following the structure: yourproject/yourapp/middleware The folder middleware should be placed in the same folder as settings.py, urls, templates… Important: Don’t forget to create the init.py empty file inside the middleware folder so your app recognizes this … Read more