Thanks. I discovered Firebug while working on this site. It really is a web developers dream.
Andrew Ⓙⓐⓚⓔ wrote: > I think you're going to have to install winProxy, and see for yourself > exactly how the ajax is failing... or just tell them to run Samba (I > hadn't heard of it either) > > I debug most of my ajax with firefox+firebug. > > On 2/7/07, *Andrew Graaff* <[EMAIL PROTECTED] > <mailto:[EMAIL PROTECTED]>> wrote: > > I am not sure if it happens with the contact page. I will check > tomorrow. All the urls are relative though. Actually I tried changing > urls to be absolute paths but that gave a javascript error. > > The page that I have tested is the > http://www.gautengfilmdirectory.org.za/dir page. There is a lot > happening on this page. Each time a listing for a category is > loaded I > think it makes 4 or 5 AJAX requests. I tried changing the header to > text/html on the server side on the directory page but that did not > help. I spoke to the user with the difficulties IT guy. He said they > have two separate proxy servers. When he tried the page without the > proxy and it worked fine. He then tried the page through the other > proxy which he said was 'SAMBA' and it worked fine. So it seems > like it > has something to do with WinProxy. I must admit that I did not know > SAMBA was also a proxy server. > > Also one more thing. If you turn javascript off then everything will > work because there is a page refresh version version for search > engines > and screen readers etc. Both the AJAX and the page refresh > version of > the directory use the same HTML templates to generate the listing > content so I am sure it is the combination of $.post and WinProxy > causing the problem. Could it be that because the return data > does not > have the <html> and <head> tags the proxy is blocking it? > > My plan was to: > > 1. Ask to see the relevant proxy log entries. > 2. Create my own log file on the server side to see if the AJAX > request > was being allowed through the proxy, which would imply it was the > return > data that was causing the problem for the proxy. > 3. Try sending the <html> and <head> and maybe the doc type tags > in the > server response. > > Lastly I was wondering if proxy servers did create problems for AJAX > requests in general or if my problem is a very isolated incidence. > > Thanks in advance. > Andrew > > _______________________________________________ > jQuery mailing list > [email protected] <mailto:[email protected]> > http://jquery.com/discuss/ > > > > > -- > Ⓙⓐⓚⓔ - יעקב ʝǡǩȩ ᎫᎪᏦᎬ > ------------------------------------------------------------------------ > > _______________________________________________ > jQuery mailing list > [email protected] > http://jquery.com/discuss/ > _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
