OMG. I tracked it down. It has nothing to do with signals nor with https. I
had a setting wrong on my production box that sent a request to the wrong
location. Stupid! Thanks regardless for responding and trying to help.
On Friday, November 13, 2015 at 1:18:14 PM UTC-6, James Schneider wrote:
>
On Fri, Nov 13, 2015 at 11:04 AM, Shawn H wrote:
> The return is a JsonResponse instead of a redirect. The production server
> does listen on port 80, but has a permanent redirect to port 443 on the web
> server. The thing that's confusing is I'm using this pattern with other
> models, with the e
The return is a JsonResponse instead of a redirect. The production server
does listen on port 80, but has a permanent redirect to port 443 on the web
server. The thing that's confusing is I'm using this pattern with other
models, with the exception of the post_save signal, and I have no problems
On Fri, Nov 13, 2015 at 9:45 AM, Shawn H wrote:
> I have a post_save signal on a model. There are many different places
> where this model gets updated and saved, which is why I'm using the signal,
> to ensure each time the model is changed, the same code gets called. I make
> the calls to save t
I have a post_save signal on a model. There are many different places where
this model gets updated and saved, which is why I'm using the signal, to
ensure each time the model is changed, the same code gets called. I make
the calls to save the model instances via a jQuery post. When I run this o
5 matches
Mail list logo
