How can I disable the default HTML pages that Play sends back as error?
In my app I don't care about the browser and would just like to receive a HTTP failing status and message. Thanks.
Related
http://fb://profile/profile-id violates AMP html policies and has led to Google de-indexing all of my web pages. How can I open my Facebook link on Facebook app when a user click Facebook icon on my site's footer using another way? I am using AMP version for mobile.
Thanks in advance
What error messages do you get after running AMP validation?
Open your page in your browser.
Add "#development=1" to the URL, for example, http://localhost:8000/released.amp.html#development=1.
Open the Chrome DevTools console and check for validation errors.
One problem could be the protocol, use https. After updating the protocol and running validation, do you have any errors?
Trying to get my head around OAuth 2.0. I am building a cross platform google drive app using PhoneGap Build and JQM.
I am able to format the request URL correctly and on both iOS and Android. It prompts the user for ID/PW using InAppBrowser (tried child browser too). Next user gets prompt with blue button on web page to "Allow Access" just like on other google web sites/apps. On Android all is well user taps allow access and callback finds the success code and I can grab the token. On iOS I get a "Load Error" message in the status bar of InAppBrowser but I can't trap the error to see what it is. It seems as if the redirect parameter breaks things before the startLoad or endLoad event can be called to trap success/failure in the response from Google.
Playing with oauth2-playground my URL looks correct and like I said it is working fine on Android.
Anyone have any ideas what differences I need to look at with regard to iOS? Been stumped here for a couple of days. Any and all help greatly appreciated.
I have tried redirecting back to http//localhost and http//localhost/afterOauth.html where afterOauth.html is a page in the app to give the redirect something to call the startLoad/endLoad event.
Update: I really think the problem has something to do with the redirect I give the original Google request. If I change "localhost" to urn:ietf:wg:oauth:2.0:oob which shows up in the google documentation both Android and iOS behave the same. They take me to a page saying "Please copy this code, switch to your application and paste it there" With the code=4/MyCode below it.
Also, I added a loaderror callback. It does not fire on Android but does on iOS giving error code -1004 and error message: could not connect to the server. However in the event.url of this loaderror it clearly shows the code=4/myCode. What is the missing link here for iOS and successful OAuth between Google?
We've integrated a like button into the site.
Sample page:
www.2knowb440.com/agent/sergey-koltunov
How ever is I try to like a page A popup opens and closes right away.
In the console an error logged:
Unsafe JavaScript attempt to access frame with URL http://www.2knowb440.com/agent/sergey-koltunov from frame with URL http://www.facebook.com/plugins/like.php?channel_url=https%3A%2F%2Fs-static.ak.fbcdn.net%2Fconnect%2Fxd_proxy.php%23cb%3Df2efa6a644%26origin%3Dhttp%253A%252F%252Fwww.2knowb440.com%252Ff1675ba004%26relation%3Dparent.parent%26transport%3Dpostmessage&extended_social_context=false&href=http%3A%2F%2Fwww.2knowb440.com%2Fagent%2Fsergey-koltunov&layout=button_count&locale=en_US&node_type=link&sdk=joey&send=true&show_faces=false&width=150. Domains, protocols and ports must match.
What am I missing?
Thanks,
Shurik
I viewed the public source of your page and see you are loading alot of javascript files before starting facebook's javascript sdk.
Try loading and initializing Facebook just below the < body > tag.
If error persists i would suggest using the i-frame version of the like button with out send.
I am requesting aspx page which is using reportviewer control and returning html.
Problem faced:
IOS 5 : It fails to render this html on first attempt. But when you close the app and log in again, Report is getting rendered properly after a long time.
IOS-4 : It works fine there, that is, html is getting rendered properly in first attempt on webview.
Research:
1)On browsers firebug, I saw that aspx url itself making multiple internal requests, that is, 1 main aspx is calling internally urls such as
a)http://..../..../Reserved.ReportViewerWebControl.axd?ReportSession=.....
b)about blank
2)When I compare IOS-4 and IOS-5 request logs, I saw there is requests mismatch. In IOS-4, there were 6 requests in total where as in IOS-5 there were 5 requests. In some of the request,webview didfinishload delgate not getting fired.
3)I tried with google.com, its getting rendered properly on both IOS.
4)I pasted the url on safari browser of iphone,the report is getting displayed properly.
I am using this:
[wvDisplayHTMLURL loadRequest:[NSURLRequest requestWithURL:[NSURL URLWithString:strURLHTML]]];
where strURLHTML contains aspx url and wvDisplayHTMLURL is webview.
Is the problem is from iphone side or server side(Ajax/Javascript)?
Any one has solution for this? Where am i wrong?
Apple seems to have made some changes in the WebView control for iOS 5.
I think your best option would be to identify and solve this issue from server side.
I'm writing a ajax chatting webapp, just to test working with GWT.
To simulate server side push of chat messages from the server to the browser, I have a XHR request running behind. It all works fine - except on Chrome, the browser is displaying a loading icon (a spinner) because of the XHR request on background.
Is there any way to avoid this? I've tested it in Firefox, and it doesn't display such behavior.
EDIT - I found the solution. http://groups.google.com/group/google-web-toolkit/browse_thread/thread/a0330cb47e05c485?fwc=2
quoting the GWT groiup post:
Chrome shows the loading indicator if connection was made immediately
from the "body onload()", i.e. from onModuleLoad().
Chrome shows the loading indicator if connection was made immediately from the "body onload()", i.e. from onModuleLoad().
No, there is now way to disable this.
All AJAX requests cause Chrome to display this. I'm guessing it's for security reasons. (The user is aware of any AJAX requests that he/she might not be aware of.) Also, it indicates that data is being fetched - a type of status indicator.