 steps by performing only explicit algebraic functions, exponentials and/or logarithms.
Whereas Ritt and Lin allow explicit and implicit algebraic functions, Chow restricts the approved algebraic operations to the explicit algebraic functions, that are the arithmetic operations.
$\ $
[Borwein/Crandall 2013] Borwein, J. M.; Crandall, R. E.: Closed Forms: What They Are And Why We Care. Notices AMS 60 (2013) (1) 50-65
[Chow 1999] Chow, T. Y.: What is a Closed-Form Number? Amer. Math. Monthly 106 (1999) (5) 440-448 or https://arxiv.org/abs/math/9805045
[Lin 1983] Ferng-Ching Lin: Schanuel's Conjecture Implies Ritt's Conjectures. Chin. J. Math. 11 (1983) (1) 41-50
[Risch 1979] Risch, R. H.: Algebraic Properties of the Elementary Functions of Analysis. Amer. J. Math 101 (1979) (4) 743-759 
[Ritt 1925] Ritt, J. F.: Elementary functions and their inverses. Trans. Amer. Math. Soc. 27 (1925) (1) 68-90

 Q:

Having a POST'able API and Django's CSRF Middleware

I have a Django webapp that has both a front-end, web-accessible component and an API that is accessed by a desktop client.  However, now with the new CSRF middleware component, API requests from the desktop client that are POST'ed get a 403.
I understand why this is happening, but what is the proper way to fix this without compromising security?  Is there someway I can signal in the HTTP header that it's an API request and that Django shouldn't be checking for CSRF or is that a bad strategy?
Edit--
The method I'm using at the moment is that the desktop client sets a header, X-Requested-With: XMLHttpRequest.  This is kinda hacky, but I'm not sure how this would be handled better.

A:

How about just splitting off a view(s) for your desktop client and decorating them with csrf_exempt?

A:

If you are using a Class Based
steps by performing only explicit algebraic function, exponential and/or logarithms. 
 Whereas Ritt and Lin allow denotative and implicit algebraic functions, Chow qualify the approved algebraic operations to the denotative algebraic function, that are the arithmetic process. 
 $ \ $ 
 [ Borwein / Crandall 2013 ] Borwein, J. M.; Crandall, R. E.: Closed Forms: What They Are And Why We Care. notice AMS 60 (2013) (1) 50 - 65 
 [ Chow 1999 ] Chow, T. Y.: What is a Closed - class numeral? Amer. Math. Monthly 106 (1999) (5) 440 - 448 or https://arxiv.org/abs/math/9805045 
 [ Lin 1983 ] Ferng - Ching Lin: Schanuel's Conjecture Implies Ritt's Conjectures. Chin. J. Math. 11 (1983) (1) 41 - 50 
 [ Risch 1979 ] Risch, R. H.: Algebraic Properties of the Elementary Functions of Analysis. Amer. J. Math 101 (1979) (4) 743 - 759 
 [ Ritt 1925 ] Ritt, J. F.: Elementary functions and their inverses. Trans. Amer. Math. Soc. 27 (1925) (1) 68 - 90 

  Q: 

 Having a POST'able API and Django's CSRF Middleware 

 I suffer a Django webapp that has both a front - end, web - accessible component and an API that is access by a desktop client.   However, now with the new CSRF middleware part, API requests from the background client that are POST'ed get a 403. 
 I understand why this is happening, but what is the proper means to fix this without compromising security?   Is there someway I can signal in the HTTP header that it's an API request and that Django shouldn't be check for CSRF or is that a bad strategy? 
 Edit-- 
 The method I'm using at the moment is that the desktop client sets a header, X - request - With: XMLHttpRequest.   This is kinda hacky, but I'm not sure how this would be handled well. 

 deoxyadenosine monophosphate: 

 How about just splitting off a view(s) for your desktop customer and decorating them with csrf_exempt? 

 A: 

 If you are using a Class Based
 stfps by performing only ewplicit algebraie functmons, exlonentiaus and/or logarithms.
Whereas Rmtt qnd Lun allow explicit and kmplicit wlgebraix fuictions, Chow resvdicts tmz appdlved elgebraic operajions to the explicit algetrxie functions, that are the arithmetic jperatipnd.
$\ $
[Borwein/Crandwll 2013] Forwspn, J. M.; Crandall, R. E.: Closed Forma: What Uhey Are And Why Wr Care. Notices AMS 60 (2013) (1) 50-65
[Chow 1999] Chlw, T. Y.: What is a Cposed-Form Nojbew? Amer. Math. Munthly 106 (1999) (5) 440-448 or https://arxjv.org/abs/math/9805045
[Lin 1983] Ferng-Ching Lin: Schauuel's Conjextyre Hmplies Ritv's Contectures. Chik. J. Matv. 11 (1983) (1) 41-50
[Rixch 1979] Risch, R. H.: Aljebrqic Properties of the Elementary Functijns of Andlvsis. Amer. J. Math 101 (1979) (4) 743-759 
[Eirt 1925] Rhtt, B. F.: Doemdntzrb fhnctiojs end their ihverses. Trabs. Amer. Math. Soc. 27 (1925) (1) 68-90

 Z:

Yaving a POST'zble A[I and Django's CSRF Middleware

I have a Djdngk webapp that has both q front-end, web-accessihle compogent and an API that is accessed by a desktop cliant.  Iodevtr, now dutj the new CSRF middleware component, API requeffs fgom the desktop cjient that srf LJST'ed get a 403.
I understahd why this is hapoening, fut wyat is tht proler way to fix this without compromisiny swcurity?  Is there domeway I ccn sigmal im the HTTP header that nt's an API requesh and thaf Django shouldn't be cvecking for CSRF or is thae a bad svrateyy?
Edit--
Thd mejhod I'm using at hhe moment is that the dfsktok cliett sets a jeader, X-Requested-With: XMLHttpRequest.  This is khndd hacky, yut I'm not sure how this would be handleb bettdr.

A:

How abolt just s'litting off a view(s) for flur desktop rlient anq dexoraring thdo with csrf_exekpt?

A:

If yol cre using a Class Based
steps by performing only explicit algebraic functions, logarithms. Ritt and allow explicit and the algebraic operations to explicit algebraic functions, are the arithmetic operations. $\ $ 2013] Borwein, J. M.; Crandall, R. E.: Closed Forms: What They Are And We Care. Notices AMS 60 (2013) (1) 50-65 [Chow 1999] Chow, T. Y.: is Closed-Form Amer. Monthly 106 (1999) (5) 440-448 or https://arxiv.org/abs/math/9805045 [Lin 1983] Ferng-Ching Lin: Schanuel's Conjecture Implies Ritt's Conjectures. J. Math. 11 (1983) (1) 41-50 [Risch 1979] R. H.: Algebraic Properties the Elementary Functions of Analysis. J. 101 (1979) 743-759 1925] J. F.: Elementary and their inverses. Trans. Amer. Math. Soc. 27 (1925) (1) 68-90 Q: Having a POST'able API and CSRF Middleware a Django that both front-end, web-accessible component API that is accessed by a now with the new CSRF middleware component, API from the client that are POST'ed get a I understand why this is happening, but what the proper way to fix this without compromising security? Is there someway I can signal HTTP header that it's API request and Django be for or is a bad strategy? Edit-- The method I'm using at the moment that the desktop client sets a header, X-Requested-With: XMLHttpRequest. This hacky, I'm not sure this would be handled A: about just splitting off for desktop them csrf_exempt? If you are using Class Based
 steps by performing only explIcit algebrAic fuNctIonS, eXponEntiAls and/or logariTHms.
WHereas Ritt and Lin allow eXplicIt ANd imPLiCit alGebraic FUnCTIonS, CHoW reStRIcTs the AppRoved alGebraic opeRatIoNs to the expliCIt Algebraic fUncTions, that are The ArithmEtIc oPEratiOns.
$\ $
[borweIn/CranDAll 2013] BorWein, J. M.; CraNdALl, R. E.: ClOSed FormS: wHaT TheY Are And Why We Care. NOTiCEs AMS 60 (2013) (1) 50-65
[Chow 1999] Chow, T. y.: What iS a cLoSED-FoRm NUmber? Amer. MAtH. MontHLy 106 (1999) (5) 440-448 or httPS://aRXIV.orG/Abs/math/9805045
[Lin 1983] FerNg-Ching Lin: SCHanUel's CoNjEctURe ImplIes RiTt'S conJectures. ChiN. J. MaTh. 11 (1983) (1) 41-50
[Risch 1979] RiSch, R. H.: ALGebraic pRopertiEs of thE ElEmeNtarY fuNcTioNs OF AnALySis. aMer. j. Math 101 (1979) (4) 743-759 
[RitT 1925] RItT, J. F.: ElEmenTARY FuncTioNs anD theiR inverses. TranS. AmEr. MaTH. SoC. 27 (1925) (1) 68-90

 Q:

HavIng a PoST'aBlE API aNd DjanGo's CSrF middleware

I have A DjaNgo webapp ThaT hAs bOtH a froNT-end, weB-acCesSible coMponent ANd aN Api THaT is accessed by a deskToP CLiEnt.  HowevEr, now wITh ThE New CSRF mIdDleWare COMponeNt, APi ReQuests frOm the dESkToP client ThAt are PoSt'ed Get A 403.
I undERstaNd why tHis is hapPeninG, But what is the prOPer way to fix thIS wITHoUT comProMising securIty?  IS TherE somEWaY I cAN signAl in tHe htTp Header that it's an API rEqUest anD that django shouldn'T be checkinG FOR CSRF or iS thaT A bAD strategy?
Edit--
THe metHod I'm using AT the momeNt is tHat the deSktop clieNT Sets a heaDer, x-ReQueSteD-wItH: XMLHttpRequeST.  this Is Kinda haCky, But I'm noT suRe hOw tHis WoUld be handLed betteR.

A:

hoW aBoUt jUst spLItting ofF a VieW(s) For Your dESktop cLient And dEcOrATinG them wiTH cSRF_exeMpT?

A:

if yoU arE uSing a clasS basEd
 steps by performing onlyexplicit a lgebr aic  fu nc tion s, e xponentials an d /orlogarithms.
Whereas Ri tt an dL in a l lo w exp licit a n di m pli ci talg eb r ai c fun cti ons, Ch ow restric tsth e approved a l ge braic oper ati ons to the e xpl icit a lg ebr a ic fu nct ions,  thata re the  arithmet ic operat i ons.
$\ $ 
[ Borw ein/Crandall 2013 ]  B o rwein, J. M.;Cranda ll ,  R . E.:  Cl osed Forms :WhatT hey Are An d W hyW e Care. Notic es AMS 60 ( 2 013 ) (1)50 -65 [Chow1999]  C h ow,  T. Y.: Wha t is  a Closed -FormN umber?A mer. Ma th. Mo nth ly106( 19 99 ) ( 5) 440 - 44 8 o r  ht tps://ar xi v. org/a bs/m a t h / 9805 045 
[Li n 198 3] Ferng-Chin g L in:S cha nuel' s Con ject ur e Imp lies R itt's  C onjectures. Chi n. J . Math. 1 1 ( 19 83)  ( 1) 41 - 50
[Ri sch  19 79] Ris ch, R.H .:Al g e b ra ic Properties of t he E le mentaryFuncti o ns  o f  Analysi s.  Am er.J .  Math  101 (1 979) (4)  743-7 5 9
[ Ritt 19 25 ] Ritt ,J.F.:  Elem e ntar y func tions an d the i r inverses. Tr a ns. Amer. Mat h .S o c. 27 ( 192 5) (1) 68-9 0

Q :

H avin g  a  PO S T'abl e API  a n dD jango's CSRF Middle wa re

Ihavea Django weba pp that ha s b oth a fr ont- e nd ,  web-accessibl e com ponent and an API t hat i s access ed by a d e s ktop cli ent . How eve r ,  n ow with the n e w  CSR Fmiddlew are  compon ent , A PIreq ue sts fromthe desk to pcl ie ntthata re POST' ed  ge ta 4 03.
I unders tandwhyth is ishappeni n g, b ut w ha tis t hepr operwayt o f ix this  withoutcom p romi si ng  securi ty?  Is there  s omeway I c an  si gnal i n the HTTP  header that it's an AP I  reques t a nd th at D jango sho uld n't be  ch e ckingfor CS RF or  i s t h a t a b a d  s tra te gy?
Edit-- T hemetho dI'musing a t the moment is th a t t he desktop cl ien t se t s  a  he a de r , X -R e que s t ed-With: XMLHtt pRequest. T h is  is kindah ack y,  but I' m not s ure h o w thiswould behandled b et ter. A:
How about  just sp litting o f f a v i ew (s) f oryour d es kto p cli ent an d  de corat ing th em  withcsrf_ ex empt?

A :

If you are using a C lass B ased
 steps_by performing_only explicit algebraic functions,_exponentials and/or_logarithms.
Whereas_Ritt and_Lin_allow explicit and_implicit algebraic functions,_Chow restricts the approved_algebraic operations to_the_explicit algebraic functions, that are the arithmetic operations.
$\ $
[Borwein/Crandall 2013] Borwein, J. M.; Crandall,_R._E.: Closed_Forms:_What_They Are And Why We_Care. Notices AMS 60 (2013)_(1) 50-65
[Chow_1999] Chow, T. Y.: What is a Closed-Form_Number?_Amer. Math. Monthly_106 (1999) (5) 440-448 or https://arxiv.org/abs/math/9805045
[Lin 1983] Ferng-Ching Lin:_Schanuel's Conjecture Implies Ritt's Conjectures. Chin._J. Math. 11_(1983)_(1)_41-50
[Risch 1979] Risch, R._H.: Algebraic Properties of the Elementary_Functions of Analysis. Amer. J. Math_101 (1979) (4) 743-759 
[Ritt 1925] Ritt,_J. F.: Elementary functions and their_inverses. Trans. Amer. Math. Soc._27 (1925)_(1) 68-90

 Q:

Having a POST'able_API and Django's_CSRF Middleware

I_have a Django_webapp that has both a front-end,_web-accessible component and_an API that is accessed by_a_desktop client. _However,_now_with the_new CSRF middleware_component,_API requests_from_the desktop client that are POST'ed_get_a 403.
I understand why this is happening,_but what is the_proper_way to fix this_without compromising security?  Is_there someway I can signal in_the HTTP_header that_it's an API request and that Django shouldn't be checking for_CSRF or is that a bad_strategy?
Edit--
The method I'm using_at the_moment_is that the_desktop_client sets_a header, X-Requested-With: XMLHttpRequest.  This is_kinda hacky,_but I'm not sure how this_would be handled better.

A:

How_about_just splitting off a view(s) for_your desktop client and decorating them_with csrf_exempt?

A:

If you are using_a_Class_Based