MoovWeb: Redirect loop when visit m.site.com using en emulator or mobile device - moovweb

I am kind of new to moovweb. We have a site hosted locally. When we access m.site.com using Chrome or IE, I am able to see the mobile version of the site. However, when I use an emulator in Chrome or IE, I get a 'redirect loop' message.
Do you know what could cause this redirect loop?
Is this a configuration setting issue?
Thanks,

Thanks to Cagri's comment I was able to figure out what the issue was.
It turns out that I was not handling properly the request when it came from Moovweb and this caused the request being redirected. I checked for the Moovweb header 'Via: 1.0 Moovweb'.
Thanks

Related

Google AdSense ERR_ADDRESS_INVALID

My website has just been approved by AdSense, and I tried to put some basic display ads on the site.
I've set up the ad, and pasted the HTML Code in my project.
When I visit the website, the console says:
Failed to load resource: net::ERR_ADDRESS_INVALID (at adsbygoogle.js:1)
I thought it was a problem of my website, but when I try to manually open the adsbygoogle JS, my browser also says ERR_ADDRESS_INVALID.
Anyone knows what to do?
Thanks in advance
Never mind, it was because of my Windows hosts file... Some program I've used earlier, blocked a lot of Hosts through it.

out of scope error shown in ajax spider attack in zap

I am using OWASP ZAP for security testing. I tried to do Ajax spider attack on my admin dashboard page. But in the message, out of scope is shown and browser is also not opening. What shall I do to fix this and open browser and to perform this test?
By default ZAP will only follow URLs that are in the same domain, otherwise it could end up trying to spider the whole internet :)
Look at the URLs it is reporting - 'http://detectportal.firefox.com/success.txt' - these are not in the same domain as your app, and are almost certainly not part of it.
So thats not the problem. Which browser and version are you using? Have you checked that ZAP is up to date?
You'll probably get more (and faster) help on the ZAP User Group :) https://groups.google.com/group/zaproxy-users
I tried again by re-installing ZAP. then it worked fine as shown in screenshot. also the webpage is opened in the browser.

Facebook App Not Displayed Insecure Content Message In Chrome

I've been trying to get to bottom of this problem for a few hours but I can't seem to fix it, I've seen other questions similar to this and tried to use those to implement a fix for my problem but to no avail.
I've built a facebook contest canvas app which displays fine independantely but when I link it to a facebook page (as a link to a new contest) chrome no longer displays is and gives the following warning:
The page at 'https://www.facebook.com/contest/app_xxxxxxxx' was loaded over HTTPS, but ran insecure content from 'http://mydomain.com/': this content should also be loaded over HTTPS.
I've learned partly by trawling this site that the chrome security is fussier, and the app loads correctly, without errors in FireFox and IE but I can't find any resources that are loaded from a non https source.
I have been through with firebug checking in the net tab and checked that all of the loaded resources are using https (the png images, the jpg images, the css files and the jquery js files which are all hosted on the same server that has the certificate), I have even tried hosting the transitional dtd doc itself but nothing seems to make the warning go away and the app display correctly.
In the other similar questions it seems that there are either resources sourced from non-https sources or there are ssl switches used in the javascript library for facebook passed before the fb init.
The problem is that I am using only the php sdk not the js one (although I am using version 1.9 of jquery, hosted on my server) and I could find no similar ssl specific settings there.
If someone could give me a tip about how I could investigate further, what I might be missing or is familiar with this issue I'd be interested to hear about it.
Thanks a lot.
David
Facebook requires the app to come from https:// you need an ssl certificate on your server and to enable ssl. in the Facebook app settings change secure url to https://mydomain.com url
I did have a similar issue recently (but it only caused issues on IE10) and I resolved that by adding P3P header
header('P3P:CP="IDC DSP COR ADM DEVi TAIi PSA PSD IVAi IVDi CONi HIS OUR IND CNT');
Found the solution!
In the facebook app settings, if the page tab url is specific to a page e.g. https://www.mydomain.com/index.php, chrome doesn't complain with the insecure content message but if you reference a directory the error is propogated. I found this confusing since the 'canvas' urls need to be directories.
I hope this answer will save someone a few hours! :)

Getting blank signed request from facebook in ie only

When I deploy my facebook app to a remote dev I seem to get a blank signed request returned but only in IE, any ideas on if this is a known IE bug?
Yup, this happens because of p3p policy and how internet explorer behaves with that. You can fix it by sending the following header data in your web application.
P3P: CP="CAO PSA OUR HONK"
You can find a detailed post on this in the following URL
http://hasin.wordpress.com/2011/09/30/story-about-blue-e-iframed-web-application-wastage-of-6-hours-and/
Hope it will help.

meta refresh for redirection not working in BlackBerry

I asked this question here but don't get reply so far. I hope posting it too here is ok.
For page redirection, in a mobile site development, I am using
<meta http-equiv="refresh" content="0;URL=/pagetwo.jsp"/>
because it is required to work when Javascript is off.
However, I find it working only in BlackBerry (BB) simulator, not in real BB (I tried with BB 8250 and 9700).
Could anyone help me please, what could be the reason.
Thanks.
Using meta for refreshing the browser isn't a good idea for a number of reasons (disables back-button, etc) and what's probably happening is your other blackberry has an accessibility issue where it won't let pages refresh themselves. Try setting it in the server-side HTTP response if you can
According to BlackBerry Browser documentation article "HTML element: <meta>" meta refresh isn't available until software version 3.7 or later.