The current request URI does not match the URI last updated for dsp:page (XXX.jsp?XXX != XXX.jsp). This may result in out of order or lost content by the attempt of dsp:include to include 'XXX.jsp'. Please make sure the contents of each JSP page containing a dsp tag are wrapped with dsp:page.
This message is showing up as a warning in the logs when I try to use dsp:include on certain jsp pages of our ATG mobile application.
I am working with an older codebase and have scanned through all the surrounding included jsps and they are all correctly wrapped with "dsp:page"
The AssemblerPpelineServlet grabs the RequestURI and obtains the forwardURL from the cache appending a querystring. This causes an apparent mismatch.
I cannot find any reference to this warning message anywhere and would be greatful if anyone could provide any insight.
Related
I am developing a component in joomla 2.5, my component sends a request to some url and gets the response object. If i pass wrong url, joomla takes me to the default page of Error : 500 - No response code found . I want that if user install my component and mistakenly they put wrong url , it should show some custom error message/page which should more meaningful to non-programming person rather than taking user to default error page. Is there some way to add this type of functionality in Joomla without editing template/error.php file in core.
You should have an error.php file in your template, if you don't add one and make it look the way you want. also remember that when you turn debugging off you won't get the stack trace etc.
However error 500 indicates something different than that the url does not exist ("wrong URL"), which would be a 404. 500 is an internal server error and you need to check your logs to figure out what is causing it.
I have just upgraded from kendoui.web.2013.1.514 to kendoui.web.2013.2.716 and have noticed that in the parts of the code where I require (through require.js) a certain kendo.culture.xx-XX.min.js file that also an unsuccessful request for kendo.core.min.js happens and I get an error in the console.
This did not happen with kendoui.web.2013.1.514 and I think this part inside the kendo.culture.xx-XX.min.js files might be to blame:
("function"==typeof define&&define.amd?define:function(e,n){return n()})(["../kendo.core.min"]
Also this reference to kendo.core appears to only be present in the minified versions. Note that I already have kendo.web.min.js fully loaded and the app works fine even with the invalid request so is this a bug?
If you are using the bundles (i.e. kendo.web.min.js) then you shouldn't use RequireJS to load them or any culture files.
I'm sorry that the documentation didn't mention it, I just added a section to explain this.
I tried to claim "Insight for my website" and i get the error "No admin data found at root webpage http://akcja-nikon.pl/. Insights requires admin data at this root webpage for the specified URL akcja-nikon.pl"
Admin tag data is there, i triple checked it, on both index.php and pickup.php (index redirects to pickup - in case you ask). I've done it almost a hundred times on all my other domains and never had a problem with that. I started having issues last week on this and one more domains.
Debugger scraps weird content for the URL an breaks after the first line on the HTML code
https://developers.facebook.com/tools/debug/og/object?q=akcja-nikon.pl%2Fpickup.php
and flags the error in red "Can't Download: Could not retrieve data from URL."
Any ideas? Maybe some weird Facebook cache?
Admin tag data is there, i triple checked it, on both index.php and pickup.php (index redirects to pickup - in case you ask).
No, it does not.
Your index.php redirects to agegate.php via JavaScript – which the Facebook scraper doesn’t care about.
And calling agegate.php directly, without any cookies set (which the scraper does not care for either), delivers a just an error message,
<br />
<b>Warning</b>: mysql_fetch_array(): supplied argument is not a valid MySQL
result resource in <b>/home/marketingpic/include-pl.php</b> on line <b>38</b>
together with an HTTP status code 302 Moved Temporarily and a faulty Location header that just says Location: pickup.php. (Faulty, because a fully qualified URL is required as value for a Location header by definition.)
And if I call your pickup.php, again without any cookies, it tries to send me back to index.php again (and again with a faulty Location header).
No idea, what exactly you are trying to accomplish here – but the way you are doing it right now, seems to be quite a nonsense.
i cant verify my webapp using maven-failsave because the web-jetty.xml referenced a missing dtd (http://jetty.mortbay.org/configure.dtd).
Any ideas? Can i disable the dtd-check?
Where can i get the content of http://jetty.mortbay.org/configure.dtd?
old one should work, I'll look into that, but you can also get it at:
http://www.eclipse.org/jetty/configure.dtd
[edit] An update on this:
We have a number of redirects in place as we try and keep the really old xml file doctypes valid. We recently wired up a redirect from jetty.codehaus.org to www.eclipse.org/jetty which has resulted in a number of validation errors on these old urls. This is being addressed but if it impacts you updating to www.eclipse.org/jetty/configure.dtd is the best solution so the redirect game is no longer played.
i try to scrap a web page. I use Nokogiri/ Mechanize. so if i make
page = agent.get(url)
page.class
=> Mechanize::File
, sometimes i get a page object sometimes a file object. but what i need is, everytime a page object. i tried to add a pluggable_parser for plain/text but this don't work for me.
have anyone an idea how i can fix it, or how i can find out the content-type from a file object or know, how i can cast a file to an page object?
Thanks Michael
Most likely the page you're requesting is unavailable and the server returns a plaintext error page.
See the docs on Mechanize::File.
The content type is in page.response['content-type'].
It's definitely possible to change the content type of the response and then create a Mechanize::Page from the data without having to download it again - but I don't think that would give you anything useful.
Check the response code as well, it's in page.code.