Allow scripts to send response codes other than 200 [36759757]

Assigned

Feature Request

Status Update

No update yet.

Description

[Deleted User]

created issue #1

Aug 21, 2013 03:09PM

Request Summary:

It sure would be nice to be able to send response codes other than 200 in a google apps script.

The particular use case I've run into is that I created a REST service based on a google spreadsheet + varnish, and in order to have consistency with other REST services, would like to return 404 when an id lookup fails. (/book/123 rather than /books/?author=Twain)

I can imagine other use cases: 304 if the script is pulling from a cache rather than re-running business logic, 400 if the request failed validation, etc.

I searched the issues list and I don't think this feature has been requested before.

I'm not alone:

http://stackoverflow.com/questions/15235783/in-google-apps-script-how-can-i-set-the-http-response-code-for-a-service-i-impl

Thanks.

Comments

[Deleted User] <[Deleted User]> #2Jul 15, 2015 12:45PM

Definitely upvoting. If one implements i.e. a JSON rest service then being able to return useful error codes would be great. Throwing an exception results in apps script returning an html page. What's worse, the result is still 200 :/

be...@gmail.com <be...@gmail.com> #3Oct 8, 2015 12:21AM

Yes this is something that would be super helpful. Currently I have a system that works well 99% of the time but sometimes there are failures to the script and I need to have the source system retry to run the script. Any update on if or when this will be available?

sc...@gmail.com <sc...@gmail.com> #4Oct 8, 2015 08:37PM

Just wanted to add my two cents - obviously we can work around this by having the error message in the return content, but it seems like utilizing the error code would provide a more standardized approach.

gr...@igmtechnology.ca <gr...@igmtechnology.ca> #5Oct 29, 2015 12:33PM

Upvoting. I'm building a JSON REST service which will be consumed by another system. Having the system register the 200 code, but then have to turn around and dive into the body to attempt to read an HTML document to see if it _really_ succeeded is simply not intuitive.

ad...@troop1313.com <ad...@troop1313.com> #6Mar 10, 2016 08:45PM

Just tripped over this one myself... need a clean way to send back HTTP errors which are often application based

sa...@gmail.com <sa...@gmail.com> #7Jun 16, 2016 10:41AM

Upvoting. Definitely need a way to send any application based error via standard HTTP codes

pe...@gmail.com <pe...@gmail.com> #8Sep 12, 2016 05:11PM

[Comment deleted]

or...@gmail.com <or...@gmail.com> #9Oct 20, 2016 05:37PM

Yes, I'm hunger and thirst for this feature. And I'm waiting for this release.

pe...@gmail.com <pe...@gmail.com> #10Dec 16, 2016 10:32PM

Upvoiting!
Because WebHooks senders rely on HTTP response code.

el...@gmail.com <el...@gmail.com> #11Jan 27, 2017 06:28PM

The problem is, the actual response is read from the redirected location. It doesn't originate from '

script.google.com' but from the domain '

script.googleusercontent.com'. So how would the client browser differentiate between say a 404 from our script vs. from the final domain?

ry...@google.com <ry...@google.com> Apr 4, 2017 04:25PM

Assigned to ap...@google.com.

[Deleted User] <[Deleted User]> #12Aug 16, 2017 01:42PM

What is the current status of this request? Is there an eta when the feature will be released? This is a must have for the web app that I am developing.

I need the ability to send back to the requesting clients 304 responses based on logic processing the request in the script.

le...@hodai.org <le...@hodai.org> #13Jul 4, 2018 12:25PM

We would also love this feature to be developed.

Regards,

-l

co...@colinscloud.com <co...@colinscloud.com> #14Dec 18, 2018 10:10PM

any status on this? It would be really helpful? to have this

br...@gmail.com <br...@gmail.com> #15Dec 19, 2018 12:35AM

cs...@gmail.com <cs...@gmail.com> #16Nov 10, 2019 05:29PM

ze...@gmail.com <ze...@gmail.com> #17Dec 15, 2019 01:10AM

lu...@theotcentre.co.uk <lu...@theotcentre.co.uk> #18Mar 5, 2020 03:10PM

ps...@gmail.com <ps...@gmail.com> #19Mar 16, 2020 07:39PM

nn...@gmail.com <nn...@gmail.com> #20Mar 28, 2020 09:00PM

UPVOTING!

Ni...@nikonovs.com <Ni...@nikonovs.com> #21Mar 28, 2020 09:01PM

ra...@gmail.com <ra...@gmail.com> #22May 4, 2020 02:30PM

so...@antevas.in <so...@antevas.in> #23May 4, 2020 06:42PM

el...@ignitionit.com <el...@ignitionit.com> #24May 26, 2020 10:53PM

ti...@gmail.com <ti...@gmail.com> #25Jul 8, 2020 11:15AM

ms...@gmail.com <ms...@gmail.com> #26Jul 21, 2020 03:16PM

j....@gmail.com <j....@gmail.com> #27Aug 5, 2020 11:48AM

ih...@gmail.com <ih...@gmail.com> #28Sep 29, 2020 07:44AM

ma...@gmail.com <ma...@gmail.com> #29Nov 3, 2020 03:28PM

hi...@cuc.global <hi...@cuc.global> #30Nov 9, 2020 08:29AM

ke...@gmail.com <ke...@gmail.com> #31Dec 7, 2020 03:44PM

[Deleted User] <[Deleted User]> #32Dec 9, 2020 06:45AM

cs...@gmail.com <cs...@gmail.com> #33Dec 18, 2020 01:43AM

Hell ya.

na...@gmail.com <na...@gmail.com> #34Mar 22, 2021 03:09PM

ju...@gmail.com <ju...@gmail.com> #35Apr 30, 2021 12:43PM

th...@gmail.com <th...@gmail.com> #36May 9, 2021 09:42AM

bi...@gmail.com <bi...@gmail.com> #37Jul 13, 2021 07:09AM

ii...@legalnetwork.jp <ii...@legalnetwork.jp> #38Sep 7, 2021 03:45AM

lt...@gmail.com <lt...@gmail.com> #39Sep 23, 2021 03:46AM

ka...@boldare.com <ka...@boldare.com> #40Oct 10, 2021 02:07AM

jo...@gmail.com <jo...@gmail.com> #41Oct 30, 2021 05:27AM

pa...@gmail.com <pa...@gmail.com> #42Nov 17, 2021 01:28AM

ma...@martin.wertgen.de <ma...@martin.wertgen.de> #43Dec 9, 2021 10:38PM

da...@gmail.com <da...@gmail.com> #44Feb 19, 2022 05:32AM

bo...@gmail.com <bo...@gmail.com> #45Mar 2, 2022 11:39AM

na...@gmail.com <na...@gmail.com> #46May 6, 2022 07:40PM

nu...@gmail.com <nu...@gmail.com> #47May 7, 2022 10:30AM

+09

sc...@hansma.org <sc...@hansma.org> #48Jun 15, 2022 02:20AM

ti...@cloudkitchens.com <ti...@cloudkitchens.com> #49Jun 15, 2022 07:46PM

da...@gmail.com <da...@gmail.com> #50Jul 22, 2022 03:01PM

mi...@noonah.co.uk <mi...@noonah.co.uk> #51Jul 26, 2022 11:56AM

an...@gmail.com <an...@gmail.com> #52Jul 27, 2022 11:17AM

av...@zenconnect.fr <av...@zenconnect.fr> #53Aug 8, 2022 07:00AM

Message last modified on Aug 8, 2022 07:00AM

[Deleted User] <[Deleted User]> #54Sep 5, 2022 11:02AM

We've been waiting for 7 years o.O I'm not sure voting will do anything at this point. Nonetheless: +1

ni...@gmail.com <ni...@gmail.com> #55Sep 23, 2022 04:38PM

jo...@fd-works.co.uk <jo...@fd-works.co.uk> #56Sep 26, 2022 02:00PM

Comment has been deleted.

Message last modified on Sep 26, 2022 02:04PM

da...@rumoon.com.br <da...@rumoon.com.br> #57Sep 30, 2022 01:02PM

I don't think this is ever gonna be implemented. As it would affect GCP cloud functions revenue.

Anyway, this is silly, because Apps Script is already limited in a number of ways.

9 Years after the original Feature Request.

pu...@gmail.com <pu...@gmail.com> #58Dec 21, 2022 11:41AM

End of 2022, still waiting!

lo...@gmail.com <lo...@gmail.com> #59Dec 23, 2022 05:29PM

Hi! I'm late to the party but here is another use case. There is an issue tracker on the XML mime type randomly getting removed from the Content Service https://issuetracker.google.com/issues/228222115?pli=1 which is hard to stomach because some services like Twilio require text/xml or application/xml in the response to execute Twiml.

A workaround (if you didn't want to respond to an inbound text) could be to return a status code of 204 No Content. Since that ability is not available, that workaround is not valid. So even getting creative, we are still blocked from a valid solution. Hopefully the team at Google is able to address these issues and give us some more tools in the tool belt, because Apps Script is amazing outside of the few limitations that it has.

ba...@odontolead.com <ba...@odontolead.com> #60Feb 13, 2023 01:55PM

mi...@gmail.com <mi...@gmail.com> #61Mar 17, 2023 05:02PM

vi...@installyou.com <vi...@installyou.com> #62Apr 12, 2023 06:06PM

Comment has been deleted.

Message last modified on Apr 12, 2023 06:06PM

sa...@dexterity.ai <sa...@dexterity.ai> #63Jul 5, 2023 10:41PM

Comment has been deleted.

Message last modified on Sep 19, 2023 05:39AM

ad...@dimeda.net <ad...@dimeda.net> #64Aug 22, 2023 02:31PM

jm...@noahface.com <jm...@noahface.com> #65Oct 2, 2023 11:10PM

+1.
Its such a basic feature to be able to return an error from a script.
It is now 10 years since the original request....

ro...@opazo.cl <ro...@opazo.cl> #66Nov 8, 2023 04:57PM

+1

It's a must to receive API notifications. If you reply with 200, the sender will always thing delivering the notification was successful.

pr...@gmail.com <pr...@gmail.com> #67Dec 6, 2023 07:43PM

Message last modified on Dec 6, 2023 07:44PM

sa...@gmail.com <sa...@gmail.com> #68Dec 29, 2023 06:11AM

bo...@gmail.com <bo...@gmail.com> #69Jan 12, 2024 09:34AM

re...@refisz.hu <re...@refisz.hu> #70Jun 26, 2024 03:07PM

Goodness, this still open?! +1000

ri...@gmail.com <ri...@gmail.com> #71Jul 11, 2024 11:03PM

This is MVP for any sort of web service.

da...@dink.dating <da...@dink.dating> #72Oct 24, 2024 04:40PM

How has such basic functionality not been implemented in over 10 years? Honest question.

om...@gmail.com <om...@gmail.com> #73Dec 13, 2024 10:03AM

Please just add this now, or burn in the flames of hell

de...@gmail.com <de...@gmail.com> #74Jan 2, 2025 02:03PM

Happy new year guys, can we have this implemented in 2025???

sa...@lespace.co.jp <sa...@lespace.co.jp> #75Jan 31, 2025 11:43AM

+10000

Issue 36759757

Description

Issue summary

Comments

[Deleted User] <[Deleted User]> #2Jul 15, 2015 12:45PM

be...@gmail.com <be...@gmail.com> #3Oct 8, 2015 12:21AM

sc...@gmail.com <sc...@gmail.com> #4Oct 8, 2015 08:37PM

gr...@igmtechnology.ca <gr...@igmtechnology.ca> #5Oct 29, 2015 12:33PM

ad...@troop1313.com <ad...@troop1313.com> #6Mar 10, 2016 08:45PM

sa...@gmail.com <sa...@gmail.com> #7Jun 16, 2016 10:41AM

pe...@gmail.com <pe...@gmail.com> #8Sep 12, 2016 05:11PM

or...@gmail.com <or...@gmail.com> #9Oct 20, 2016 05:37PM

pe...@gmail.com <pe...@gmail.com> #10Dec 16, 2016 10:32PM

el...@gmail.com <el...@gmail.com> #11Jan 27, 2017 06:28PM

ry...@google.com <ry...@google.com> Apr 4, 2017 04:25PM

[Deleted User] <[Deleted User]> #12Aug 16, 2017 01:42PM

le...@hodai.org <le...@hodai.org> #13Jul 4, 2018 12:25PM

co...@colinscloud.com <co...@colinscloud.com> #14Dec 18, 2018 10:10PM

br...@gmail.com <br...@gmail.com> #15Dec 19, 2018 12:35AM

cs...@gmail.com <cs...@gmail.com> #16Nov 10, 2019 05:29PM

ze...@gmail.com <ze...@gmail.com> #17Dec 15, 2019 01:10AM

lu...@theotcentre.co.uk <lu...@theotcentre.co.uk> #18Mar 5, 2020 03:10PM

ps...@gmail.com <ps...@gmail.com> #19Mar 16, 2020 07:39PM

nn...@gmail.com <nn...@gmail.com> #20Mar 28, 2020 09:00PM

Ni...@nikonovs.com <Ni...@nikonovs.com> #21Mar 28, 2020 09:01PM

ra...@gmail.com <ra...@gmail.com> #22May 4, 2020 02:30PM

so...@antevas.in <so...@antevas.in> #23May 4, 2020 06:42PM

el...@ignitionit.com <el...@ignitionit.com> #24May 26, 2020 10:53PM

ti...@gmail.com <ti...@gmail.com> #25Jul 8, 2020 11:15AM

ms...@gmail.com <ms...@gmail.com> #26Jul 21, 2020 03:16PM

j....@gmail.com <j....@gmail.com> #27Aug 5, 2020 11:48AM

ih...@gmail.com <ih...@gmail.com> #28Sep 29, 2020 07:44AM

ma...@gmail.com <ma...@gmail.com> #29Nov 3, 2020 03:28PM

hi...@cuc.global <hi...@cuc.global> #30Nov 9, 2020 08:29AM

ke...@gmail.com <ke...@gmail.com> #31Dec 7, 2020 03:44PM

[Deleted User] <[Deleted User]> #32Dec 9, 2020 06:45AM

cs...@gmail.com <cs...@gmail.com> #33Dec 18, 2020 01:43AM

na...@gmail.com <na...@gmail.com> #34Mar 22, 2021 03:09PM

ju...@gmail.com <ju...@gmail.com> #35Apr 30, 2021 12:43PM

th...@gmail.com <th...@gmail.com> #36May 9, 2021 09:42AM

bi...@gmail.com <bi...@gmail.com> #37Jul 13, 2021 07:09AM

ii...@legalnetwork.jp <ii...@legalnetwork.jp> #38Sep 7, 2021 03:45AM

lt...@gmail.com <lt...@gmail.com> #39Sep 23, 2021 03:46AM

ka...@boldare.com <ka...@boldare.com> #40Oct 10, 2021 02:07AM

jo...@gmail.com <jo...@gmail.com> #41Oct 30, 2021 05:27AM

pa...@gmail.com <pa...@gmail.com> #42Nov 17, 2021 01:28AM

ma...@martin.wertgen.de <ma...@martin.wertgen.de> #43Dec 9, 2021 10:38PM

da...@gmail.com <da...@gmail.com> #44Feb 19, 2022 05:32AM

bo...@gmail.com <bo...@gmail.com> #45Mar 2, 2022 11:39AM

na...@gmail.com <na...@gmail.com> #46May 6, 2022 07:40PM

nu...@gmail.com <nu...@gmail.com> #47May 7, 2022 10:30AM

sc...@hansma.org <sc...@hansma.org> #48Jun 15, 2022 02:20AM

ti...@cloudkitchens.com <ti...@cloudkitchens.com> #49Jun 15, 2022 07:46PM

da...@gmail.com <da...@gmail.com> #50Jul 22, 2022 03:01PM

mi...@noonah.co.uk <mi...@noonah.co.uk> #51Jul 26, 2022 11:56AM

an...@gmail.com <an...@gmail.com> #52Jul 27, 2022 11:17AM

av...@zenconnect.fr <av...@zenconnect.fr> #53Aug 8, 2022 07:00AM

[Deleted User] <[Deleted User]> #54Sep 5, 2022 11:02AM

ni...@gmail.com <ni...@gmail.com> #55Sep 23, 2022 04:38PM

jo...@fd-works.co.uk <jo...@fd-works.co.uk> #56Sep 26, 2022 02:00PM

da...@rumoon.com.br <da...@rumoon.com.br> #57Sep 30, 2022 01:02PM

pu...@gmail.com <pu...@gmail.com> #58Dec 21, 2022 11:41AM

lo...@gmail.com <lo...@gmail.com> #59Dec 23, 2022 05:29PM

ba...@odontolead.com <ba...@odontolead.com> #60Feb 13, 2023 01:55PM

mi...@gmail.com <mi...@gmail.com> #61Mar 17, 2023 05:02PM

vi...@installyou.com <vi...@installyou.com> #62Apr 12, 2023 06:06PM

sa...@dexterity.ai <sa...@dexterity.ai> #63Jul 5, 2023 10:41PM

ad...@dimeda.net <ad...@dimeda.net> #64Aug 22, 2023 02:31PM

jm...@noahface.com <jm...@noahface.com> #65Oct 2, 2023 11:10PM

ro...@opazo.cl <ro...@opazo.cl> #66Nov 8, 2023 04:57PM

pr...@gmail.com <pr...@gmail.com> #67Dec 6, 2023 07:43PM

sa...@gmail.com <sa...@gmail.com> #68Dec 29, 2023 06:11AM

bo...@gmail.com <bo...@gmail.com> #69Jan 12, 2024 09:34AM

re...@refisz.hu <re...@refisz.hu> #70Jun 26, 2024 03:07PM

ri...@gmail.com <ri...@gmail.com> #71Jul 11, 2024 11:03PM

da...@dink.dating <da...@dink.dating> #72Oct 24, 2024 04:40PM

om...@gmail.com <om...@gmail.com> #73Dec 13, 2024 10:03AM

de...@gmail.com <de...@gmail.com> #74Jan 2, 2025 02:03PM

sa...@lespace.co.jp <sa...@lespace.co.jp> #75Jan 31, 2025 11:43AM

Add comment