How to avoid those browser warnings about mixing secure and insecure
content on a web page?
Wouldn't it be great to be able to specify a URL for a resource (be it a
script, image, iframe etc.) such that if the current page is insecure
(using a http:// scheme) the content would be fetched using
I created a ticket for this problem:
https://code.djangoproject.com/ticket/20187
--
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to django-developers+unsubscr
ot suitable for caching. That's something that my
application can handle.
Do you think this would work OK?
I'll create a ticket to track this.
Thanks,
Stephen
On Tuesday, 2 April 2013 20:03:49 UTC+1, Aymeric Augustin wrote:
>
> On 25 mars 2013, at 18:02, SteveB >
> wrote
With the change to HttpResponse made in Django 1.5, I'm finding that in my
code, which caches a generated response, results in an empty body when that
page is requested a second time. The first time the page is requested, it
is not in the cache, and the page is generated normally and added to th
Hi,
Can anybody provide an update on the request to define a BigAutoField in
Django?
We could really use this model field type without having to do workarounds
and customizations.
Can any of the Django developers comment on when this will be released?
Thanks,
Steve
--
You received this message
