In "Live HTTPS headers", a FF plugin, I see this: http://cstoolstest.tnc.org/search/search?q=conservation&collections=EAST%7CTEA&start=1
GET /search/search?q=conservation&collections=EAST%7CTEA&start=1 HTTP/ 1.1 Host: <domain> User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv: 1.9.2.12) Gecko/20101026 Firefox/3.6.12 Accept: application/json, text/javascript, */* Accept-Language: en-us,en;q=0.7,de;q=0.3 Accept-Encoding: gzip,deflate Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7 Keep-Alive: 115 Connection: keep-alive Content-Type: application/x-www-form-urlencoded X-Requested-With: XMLHttpRequest Referer: http://<domain>/search/ HTTP/0.9 200 OK There is no redirect and the status code is 200. Also, in firebug I see the request sent and in my app log, I see the request being received correctly. When I look at response in Firebug, it is empty. Eric On Nov 2, 9:49 pm, adelein <[email protected]> wrote: > You can easily look at the request/response by using firebug. > > TIP: Notice if there is a redirect. Sometimes depending on the config, > for example, if django is set to append a / at the end, meaning it > will do a redirect, then your request or response might be getting > lost in the redirect (an HTTP > 302)http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html > > When you have django running with apache config might be different. So > first step is look in firebug what requests are being made. > > On Nov 2, 3:13 pm, Reinout van Rees <[email protected]> wrote: > > > On 11/02/2010 09:29 PM, Eric wrote: > > > > I am returning a json structure in one of my views after the user > > > performs a search when I only run Django's built in server. Following > > > the asynchronous GET I get a response with the expected json > > > structure which I can then use to populate the page. > > > > However, when I have Apache in front, the response is empty. And this > > > appears to be only when I make an AJAX request since all of the other > > > requests and responses produce the expected results. > > > > I don't know how to go about troubleshooting this. > > > > Does anybody know what is going on here? Or, how to troubleshoot this? > > > Some random tips: > > > Take a hard look at what's actually being returned. Empty response, > > apparently. But what about the http status code? 200 OK or 500 > > AARGH_ERROR? Or something that's just not parsed as valid json? Or > > perhaps an invalid mimetype? > > > Useful tools: firebug (lets you inspect the headers). Or just "wget" in > > a pretty verbose mode. > > > Reinout > > > -- > > Reinout van Rees - [email protected] -http://reinout.vanrees.org > > Collega's gezocht! > > Django/python vacature in Utrecht:http://tinyurl.com/35v34f9 -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
