Status Update
Comments
je...@google.com <je...@google.com> #2
better practice and documentation about this issue will be appreciated
lx...@google.com <lx...@google.com> #3
Agreed, this is a must for me to securely pass information to a Google Webapp dopost function. URL querystrings are not secure...
lx...@google.com <lx...@google.com> #4
I see the request status has not changes for this item, is there a current update on if this feature will be implemented in the Google Webapp product?
je...@google.com <je...@google.com> #5
I stopped using Apps Script because of it being unreliable. I'm working with Firebase now, which is a Google service with enhanced capabilities.
va...@chromium.org <va...@chromium.org> #6
Not the most elegant solution but its possible to use cloud functions as a workaround. Here's a link to a post I created on the topic:
https://plus.google.com/u/0/109722946999133841016/posts/97iVtkSj6qi
je...@google.com <je...@google.com> #7
pls!!!
ab...@gmail.com <ab...@gmail.com> #8
+1 please
is...@google.com <is...@google.com> #9
+1 pls!
ko...@google.com <ko...@google.com> #10
+1 please
jc...@google.com <jc...@google.com> #11
+1 pls
va...@google.com <va...@google.com> #12
+1 please!!!
jc...@google.com <jc...@google.com> #13
A message to the authors of the more recent posts, "+1 please" comments don't really make a difference. If you really want to draw attention to this issue then you need to star it. Open the issue and click to the star at the top of the thread. The higher the "starred" count the more likely the devs at Google will notice this issue.
je...@google.com <je...@google.com> #15
+1
va...@google.com <va...@google.com> #16
Please
je...@google.com <je...@google.com> #17
+1
This is most important to access headers in doPost because of all of the modern system post a security token into the header in order to validate POst body.
This is most important to access headers in doPost because of all of the modern system post a security token into the header in order to validate POst body.
va...@google.com <va...@google.com> #18
+1
Description
Chrome Version: 111.0.5563.64
Lacros Version N/A
OS: macOS Version 13.2.1 (Build 22D68)
What steps will reproduce the problem?
(1) Connect to an SSH server
(2) Wait long enough for the computer to start its screen saver
What is the expected result?
The SSH connection stays open (or closes cleanly)
What happens instead?
The extension freezes and the page needs to be reloaded to reconnect