Infeasible
Status Update
Comments
va...@google.com <va...@google.com>
ku...@google.com <ku...@google.com> #2
Hello,
Thank you for reporting this feature request.
In order to not misunderstand it, you want to be able to insert into a document
Also, what would be your benefit of having this implemented?
Thank you!
bs...@gmail.com <bs...@gmail.com> #3
I would also like to make this request to insert new smart chips into Google Docs using both the API and Apps Script functions.
Description
I have configured Open Id using following step by step tutorial and it works as expected
However it seems API is configured to use HTTP Referer too which then it will returns 403 if there is no HTTP Referer is sent with the request or it doesn't match the website.
There are a few major issues with this approach.
1- Not all applications are web and send referer (e.g. my windows (and linux) desktop application uses google open ID to identify logged in users, does not send a referer and if I send one, it will be a meaningless made up header.
2- Some of my users are using browser Referer extension (for privacy of course) which then masks inter-website referer header if the website for two pages are not same (in this case my website and google). This causes the following request return 403
Assuming this same page is returning error if browser agent is not as expected (not listed in google) since I am again getting random 403 errors even though I am sending a fixed fake referer to API.
This is easily reproducible with "Smart Referer" extension on firefox browser
or Referer Control extension on Chrome browser
in both cases no configuration needed, install the extension and activate it and following script will always fail (screenshots)
I am attaching content of the HTML page and request and response when extension is active or inactive.
Note that using both HTTP referer and user-agent as a security header is very very wrong as user can easily modify it even with a browsers widely available in market. use of an encrypted value in a custom header, request GET or POST content instead, is more secure and preferred.
HTML Page content
When referer extension is active (running on localhost)
Request Header (identifiers redacted)
Response Header (identifiers redacted)
With same page when referer extension is not active
Request Header (identifiers redacted)
Response Header (identifiers redacted)