I want to add telephone link in the Link out suggestions of google assistant, but it don't allow me to do it as its saying only http/https urls.
Is there any custom payload which will allow me to do it?
If yes please provide me some links which might be helpful for me.
No, link out suggestions can only be HTTP or HTTPS.
If your suggestion chip links out to an external website (using
addSuggestionLink or linkOutSuggestion) the destination site must be
verified and use the same protocol (http vs https) as the URL.
(Source: https://developers.google.com/actions/assistant/responses#suggestion_chip)
Related
I want my capsule to redirect to the web browser URL on the click of a button. I am not getting anything to redirect.
Is redirection to the web browser URL from Bixby is possible?
Any help, please.
You are looking for the app punch out functionality. I would recommending looking at the documentation here for more information.
There are two ways to open an external URL from Bixby:
attribution-link (documentation)
app-launch (documentation)
In general, attribution-link is the best method of launching a web URL from within your Bixby capsule. I would highly recommend reading through the app punch out policies for guidance on where to place attribution-link and/or app-launch in your capsule's flow.
I am trying to connect to google drive and for that I am using python pydrive library. I have followed the documentation and written a snippet for connecting with google drive. But I get an error
Error: redirect_uri_mismatch
The redirect URI in the request, http://localhost:8080/, does not match the ones authorized for the OAuth client. To update the authorized redirect URIs
Here is the code of pydrive that I have executed (I have installed the pydrive library as well)
from pydrive.auth import GoogleAuth
gauth = GoogleAuth()
gauth.LocalWebserverAuth()
I am posting an image of my console.developer account, you can see I have written the address correctly as specified by the pydrive documentation. I have also added outcallback in the url but I am still getting the same error. Any help will be appreciated. Thanks
This is my client_secrets.json file content:
{"web":{,"project_id":"my-project-1532814702018","auth_uri":"https://accounts.google.com/o/oauth2/auth","token_uri":"https://accounts.google.com/o/oauth2/token","auth_provider_x509_cert_url":"https://www.googleapis.com/oauth2/v1/certs","redirect_uris":["http://localhost:8080/oauth2callback"],"javascript_origins":["http://localhost","http://localhost:8080"]}}
(I have removed client id and client secret here)
I know its a bit late now, but it may help someone who encounters this issue.
For me it was really silly. In "Authorized redirect URIs" field it must be "http://localhost:8080/" with a slash at end. In "Authorized JavaScript origins" it must be "http://localhost:8080" without a slash.
Edit Your URL and replace http://localhost:8080/ by http://localhost:8080
it works for me
You're almost there. Just add '/oauth2callback' as indicated in the greyed texts.
So, under 'Authorized redirect URIs' :
http://localhost:8080/oauth2callback
It seems that google api has changed their policies on authorized domains, i heard there's remote domain that redirect to localhost? or you can change your hosts file... it doesnt make sense, because google supports api usage on native apps, why would they need a domain name?
We're looking to do some scraping on a specific URL that uses cloudflare. Has anyone experienced issues using Zombie.js/user-agents while trying to crawl cloudflare hosted sites.
Would love some help!
I am trying to interface to an API on a client's site and I am getting a 403 error indeed. The request doesn't even reach my server.
Turning security to "essentially off" did not help. The final solution was to white-list the developer machine's IP.
The error is triggered on a single URL (json serving API) with a Java client with standards compliant libraries.
Solution:
1. try to set a rule to allow direct access for that URL
2. try setting security to weaker and weaker ("essentially off")
3. if both fails: try whitelisting
4. set up an alternate non-cloudflare url (direct.domain.com)
These will of course only work if you can negotiate with the site owners.
Backup solution: use an embedded browser that you can "frame" and "remote control" or a testing framework that does the same through a plugin, and extract the content from there (if you can)
Hope this helps.
You're probably triggering one of our security features by trying to scrape a site on us. The only option, really, would be to ask the site owner to whitelist your IP(s) to override the behavior.
i need help to only allow Google bot and Yahoo/MSN bot access to my site through .htaccess. Any help greatly appreciated.
For Google i got, not sure if that is right...
Allow from googlebot.com google.com google-analytics.com
Satisfy Any
I think your reasons for doing this are probably questionable, but the only way to really do this is by the reported User-agent (a HTTP request header), not by domain - and the reported user-agent can easily be spoofed by anyone. (This is also usually controlled through a robots.txt, but is typically for the opposite purpose - restricting crawlers, not normal users.) The servers that Google and others use to crawl sites won't have the same names or IPs as the names you listed.
For Google, some additional and official details of this are available at http://support.google.com/webmasters/bin/answer.py?hl=en&answer=1061943 . Yahoo and MSN will have similar pages.
I have been implementing the 'login through facebook' button on my e-commerce site by using the javascript sdk and the example here: http://developers.facebook.com/docs/authentication/ .
However, i have noticed that the cookie created by the sdk can be transmitted through http (as opposed to https) and I am pretty sure this is not the safest thing to do?
what do you guys recommend me to do to fix this?
Your website can ensure that it is using https for its pages that transmit the facebook token. Facebook is being flexible by enabling http or https.
If you don't want to (or can't) use https, then the question becomes what are the real risks?
China, Iran and other repressive countries do target social network users such as Facebook. But problems are far fewer in other countries.
Will your customers even notice use of http vs https? Eg the main Facebook site will work with either. They do NOT switch http users to the https protocol. (Unlike most banks.)