On Wednesday, August 6, 2014 7:51:09 PM UTC-4, Russell Keith-Magee wrote:
>
> Hi Alvaro,
>
> Firstly - congratulations - sounds like an interesting package. However,
> you may find that django-users is a better forum to announce something like
> that. Django-developer
om libraries natively
- Writing a full set of documentation
- Enhancing performance: parallel parsing, speculative rendering,
aggressive caching, etc.
However, first I'd like to get a sense of whether such work would be
useful. As always, all feedback is appreciated.
Thank you!
Yeah, I would agree with you. You should know what your csrf middleware is
doing when you enable it so you should know what cookie name, etc is being
used for your JS.
On Aug 4, 2014 12:56 PM, "Donald Stufft" wrote:
>
>
> On August 4, 2014 at 3:52:56 PM, Wes Alvaro (he...@w
t; https://github.com/search?q=settings.CSRF_COOKIE_NAME&ref=cmdform&type=Code
>
> On Monday, December 2, 2013 8:05:51 PM UTC-5, Wes Alvaro wrote:
>>
>> I agree; that's exactly the issue I'm trying to rectify. I'd like the
>> backend to be constant and ju
need to config a couple settings when I start off
> with Angular. (Another being setting X-Requested-With so request.is_ajax
> works as expected).
>
>
> On Fri, Nov 22, 2013 at 2:28 PM, Wesley Alvaro
>
> > wrote:
>
>> I've been using AngularJS with Django, bu
I've been using AngularJS with Django, but I have to override the default
CSRF cookie/header values in AngularJS since only one of the values (the
cookie name) can be overridden in Django.
This is a humble request to add a setting for the CSRF header name so that
I can maintain it as my "Angula
Call it Reinhardt, like the surname of Django :-)
On Dec 17, 2008, at 11:18 AM, Arien wrote:
>
> On Tue, Dec 16, 2008 at 8:36 PM, Malcolm Tredinnick
> wrote:
>>
>> All of this is predicated on using the word "Django" in the name,
>> which
>> is the bit I have a problem with.
>
> How is this di
Hi Rajeev,
Any help that I can provide, just ask. I think with a JSON object
containing the debug data with some structure expected by FireSymfony,
it should be easy to port it to Django or any other framework.
Regards,
Alvaro
On Oct 16, 2008, at 10:27 AM, Rajeev J Sebastian wrote
sy to port/adapt the current firebug extension
code to make it work with another framework.
Cheers,
Alvaro
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group
