Thanks Jason 🙏
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to this group, send email to google-ap
Follow https://issuetracker.google.com/issues/117814186 for resolution.
On Thursday, 15 November 2018 16:51:06 UTC-8, Indra Sumawi wrote:
>
> Hi Jason,
>
> I see. Thank you for your answer :)
>
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" grou
Hi Jason,
I see. Thank you for your answer :)
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appengine+unsubscr...@googlegroups.com.
To post to thi
Okay, thx.
For the "second gen runtimes" (php72, nodejs8, python37, go111) we are
currently not sending the Accept-Encoding header to your app, and we are
suppressing the Content-Encoding header on the response. This will change
in the next 2-3 weeks and both headers will function as expected.
Hi Jason,
During the test, I'm using runtime php72 for standard and runtime php for
flexible
--
You received this message because you are subscribed to the Google Groups
"Google App Engine" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-appeng
What runtime are you using?
On Wednesday, 14 November 2018 10:22:27 UTC-8, Indra Sumawi wrote:
>
> Currently I develop REST API using laravel framework and I deploy it to
> both Google Cloud App Engine Standard and Flexible version.
>
> When I deploy it to flexible version, it works fine. However
