CSRF token is null

Using Django Templates & Frontend
22

While I have tried to make a webserver at
https://beta.pmine.org/skincomp/
could you please see whether it works OK on yourside?

23

I didn’t get an error if that’s what you mean.

24

I mean when clicking the submit button, the header’s origin is null.
The page will display a 404. actually, I only started my frountend but not the backend
Do you mean that when you are submitting the forum the origin of your header is not null value instead of the origin value that on my side?

image
image820×308 24.5 KB

25

I am sending an Origin: null header

26

Please see my reply at CSRF token is null - #21 by KenWhitesell. I don’t think this is going to work - even if you get the Origin header fixed.

The other problem that you are going to have difficulty resolving is the CSRF token and cookie issue. The page loaded from project “A” is not going to be able to give you a CSRF token that project “B” is going to recognize. There’s also likely going to be a problem with the cookie as well.

27

I see. So, the thing that I should do is to put the two apps in the same project rather then working with the header thing or do the nginx settings rather than fixing this problem. Thanks for your help
By the way, can I ask for one more question that is it common to put the frount end and backend together in one project? Or I encounter this problem due to some special reasons (I don’t know whether I have expressed myself clearly), but I really thank you for your patience and help

28

My opinion is that you only need one app - until you encounter a situation where it is necessary to break it down into multiple apps.

I believe it is a waste of time and effort to needlessly separate tasks arbitrarily into multiple apps. I don’t see where there’s anything to be gained by doing this, and a lot of problems an potential issues as well.

I’ve done production deployments of more than 20 different Django systems, and right off-hand, I can only think of 2 that consisted of more than one app. And, I have never tried - and probably would have never thought of breaking up a project into two separate projects between “front-end” and “back-end”. To me, that just seems like the wrong way to organize a Django project.

So as I explained above, this is the only way I’ve ever done it. I don’t see any value doing it any other way.