views:

40

answers:

2

we deliver micro-site content for our client. Our content is injected into a wrapper that is supplied by another developer.

To deliver our content we host the wrapper as well as the content. The user can access this at

http://fundcentre.newireland.ie/ (try a search for 'bloxham')

For the other content that is not ours, the other developer hosts a similar (though slightly different) wrapper and delivers the content. the user accesses this here:

http://www.newireland.ie/ (try a search for 'bloxham')

The wrapper contains a search box, which does not work for us but it works for the other developer. I took a look at the network traffic with FireBug but it appears that when I do the search from the wrapper that we're hosting, I'm getting a "407 Proxy Access Denied" error. My guess is their proxy has a problem with the fact that the search is being conducted from a page hosted outside the scope of their proxy.

It was also suggested that there were javascript errors on the page that were preventing the search from executing but I can't see any. Also, I don't think I'd get as far as the proxy error if that was the case.

I don't really understand this stuff too well though, so could somebody with a bit more experience please take a look and maybe shed some light on this for me? Thanks.

A: 

It could be a problem that your tags' action are pointing to different scripts. One is pointing to "Home.aspx" and the other to "/Default.aspx". The two links are in different subdomains, so maybe you would like to change the action of the subdomain so it contains the full location of the action (ex. "http://www.newireland.ie/Default.aspx")

Zsolti
The search itself however is actually a different URL from *either* of those two.
Pointy
+1  A: 
Pointy
Thanks Pointy, your suggestion to 'return false' seems to be the solution. I agree with you about the design being thrown out. There were a lot of uninformed decisions made early in the design phase that I had no input on. It's a bit of a disgrace. However, for what it's worth it seems this problem lies with the other developer. Thanks for helping point this out.
DaveDev
I've been there too! Good luck etc.
Pointy