Re: Issue with post_save signal only when using https

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 <shawn....@gmail.com> 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 exception of the post_save signal, and I have no problems, even on https. I can save the object and return a JsonResponse no problem. It seems to be exclusively the signal that causes the issue, as far as I can tell.

That doesn't make sense. What process is generating the URL for the redirect? Have you validated that the redirect is pointing at the right location?

Where exactly are you seeing this message? Have you installed django-debug-toolbar and told it to intercept the redirects so that you can examine them?

I guess the better question is how a redirect is involved if your updates are pushed via JQuery? Or do you have other regular web forms that modify this model as well?

-James

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django-users@googlegroups.com.
Visit this group at http://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/f505eeff-7746-4c16-9a6e-6f4155070cb3%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.