This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
By the time a JSP page gets to the browser, it's just an HTML page like any other. So you can get the markup of the non-working page (View Source from browser), and compare it to the markup of the working page to see what's different.
And again, you can;t make an Ajax request to a domain other then that which served the page. You'll need to use a server-side proxy, or JSONP if all you are making are GET requests.
Joined: Jul 05, 2012
you can;t make an Ajax request to a domain other then that which served the page.
In this case even the port needs to be same?? for eg. if the page on browser has been fetched from http://ip:8080/, then the other request for http://ip:8443/ is also subject to cross domain issue??
The above behavior is with JSP implementation running on Tomcat (not the standalone html page). SO, I suspect is it really the cross domain issue as you pointed.