[google-appengine] Re: Max 10,000 file limit is not suitable for modern full featured wordpress site or any PHP app

['Nicolas (Google Cloud Platform Support)' via Google App Engine]

Hi Shaharia,

Thank you for bringing those inconveniences that you are experiencing , 
I’ll make sure to relay those to the App Engine engineering team.

In the meantime for the default 10,000 file upload issue, if you have a 
Silver, Gold, or Platinum support package you can contact a support 
representative [2] to file a proper quota increase request.

Also concerning the SMTP port 25 being block you are right we block it 
because of the risk of abuse [3] you could also be interested in other 
alternative solution like SendGrid, MAilgun or Mailjet [4].

We value our customers and take into consideration every feedback about our 
products.

[1] https://cloud.google.com/appengine/quotas#When_a_Resource_is_Depleted

[2] https://cloud.google.com/support/docs/#contacting_technical_support

[3] https://cloud.google.com/compute/docs/tutorials/sending-mail/
[4]
https://cloud.google.com/compute/docs/tutorials/sending-mail/#choosing_an_email_service_to_use

On Monday, April 15, 2019 at 9:51:02 AM UTC-4, Shaharia Azam wrote:
>
> Hello Everyone,
> I know this is a common questions but actually this is now becoming more 
> and more strange to me day by day. Why Google still feels about the hard 
> limit related to max 10,000 file? If I want to install Wordpress latest 
> version with any premium themes, few e-commerce related mandatory plugins 
> then easily from the beginning of my development this would cross 10,000 
> files. 
>
> We are a web solution provider company and we are facing few very hard 
> questions that is forbidding us to suggest GCP to our client's for their 
> needs.
>
> 1. Advance & Full featured E-Commerce site powered by Wordpress due to 
> 10,000 file limit issue.
> 2. SMTP outgoing issue due to block of Port 25. Even our own cPanel server 
> is hosted on AWS for that. Rest of our servers that doesn't need email 
> communication are on GCP.
>
> Does Google think that it is irrelevant? Even from the quota request page, 
> this file limit quota can't be increased. In this case, not only us but 
> also lots of people are going away from using GCP and specially Google App 
> Engine (our use case depends on it). So I want to hear something from any 
> internal team members about this. Is there any plan in future to remove 
> this limit or increase this limit or you are suggesting us to go away from 
> App engine to somewhere else?
>
> - @shaharia
>

-- 
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-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/4f5421d9-0dc9-4218-860d-4dbb76146c0a%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Cloud schedule targetting to a specific app engine service

['George (Cloud Platform Support)' via Google App Engine]

The appspot.com domains also support subdomains of the form 
[SUBDOMAIN]-dot-[YOUR_PROJECT_ID].appspot.com, where [SUBDOMAIN] can be any 
string allowed in one part of a domain name, excluding the . character. You 
can find related details on the "How Requests are Routed" documentation page 

. 

-- 
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-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/978ee89a-b0d1-47d5-b838-584145dc9518%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] CORS on AppEngine Java

['Les Vogel' via Google App Engine]

Hi Joshua,

First off, CORS  isn't really a protection
against CSRF.  For CSRF mitigation ideas take a look here
.
CORS is mostly a protection against asset and bandwidth theft. (See Why CORS
?)

Instead of thinking about CORS first, you really want to think about your
web application.  What assets will it be requesting and where do they
live.  Your primary assets determine the rules that work for free.  (ie.
you can always load things from the same spot).  (typically your domain or
an *.appspot.com address) . The other spots need to be told that they can
permit / give permission for your app to access the data.

As I mentioned earlier, static assets on App Engine are set in your
appengine-web.xml
 or
app.yaml 
files.  Dynamic assets will need code, for Java Servlet's it's usually
easitest to add a filter
 that runs
before the Servlet.  Other frameworks have similar mechanisms.

GoogleAPI's depend on the service your accessing.  The most common is Cloud
Storage which has a page on CORS
 and configuration
.  Other Google
properties & API's that expect to be accessed via a web application will be
configured appropriately or provide a mechanism
.

Hope that helps,

Les

On Sun, Apr 14, 2019 at 12:23 AM Joshua Fox  wrote:

> Thank you, Les,
>
> However, Google Cloud serves our content from multiple  domains besides
> our own, including appspot.com, google.com, googleusercontent.com,
> googleapis.com, and many others. How can we allow access to these domains
> (as well as our own) with  CORS headers, yet maintain security against CSRF?
>
> On Sat, Apr 13, 2019 at 1:24 AM 'Les Vogel' via Google App Engine <
> google-appengine@googlegroups.com> wrote:
>
>> [bcc: three googlers]
>> Hi Joshua,
>>
>> I read the docs
>>  a
>> bit closer and if you look under , it gives a CORS example
>> without ever mentioning CORS.  (I've asked that this gets fixed) . Again,
>> it's only for static content.
>>
>> Les
>>
>> On Fri, Apr 12, 2019 at 3:05 PM Les Vogel  wrote:
>>
>>> [bcc: a couple googlers]
>>> Hi Joshua,
>>>
>>> Sorry for the terse response earlier. The enable-cors answer will work
>>> in many cases, but is incomplete, but you'll find yourself adding it to all
>>> your pages.  Of course, a full answer is a lot more complicated and depends
>>> on what you are trying to serve and where you are serving it from.  Your
>>> static assets will need one kind of CORS headers similar to what the
>>> documentation is showing you for Go / Python.  It's been awhile since I did
>>> that for Java, so I'll need to look that up if that's what you're looking
>>> for.
>>>
>>> If you are trying to serve dynamic content that needs CORS headers, then
>>> you'll probably want to look at:
>>> https://stackoverflow.com/questions/8303162/jetty-cross-origin-filter
>>>  and https://howtodoinjava.com/servlets/java-cors-filter-example/
>>>
>>> Take a look at that, and let me know if that doesn't work for you and
>>> I'll try to look up what to change in appengine-web.xml for CORS support.
>>>
>>> Les
>>>
>>> On Fri, Apr 12, 2019 at 1:43 PM Les Vogel  wrote:
>>>
 See https://enable-cors.org/server_appengine.html

 On Thu, Apr 11, 2019 at 7:44 AM Joshua Fox 
 wrote:

> In AppEngine  Python and Go
> ,
> one defines CORS headers in app.yaml
>
> But in Java, the documentation does not mention this
>  How
> do I do the equivalent in Java?
>
>
>
> --
>
>
> *JOSHUA FOX*
> Director, Software Architecture | Freightos
>
>
>
> *T (Israel): *+972-545691165 | *T (US)*:  +1-3123400953
> Smooth shipping.
>
>
>
> --
> 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-appengine@googlegroups.com
> .
> Visit this group at https://groups.google.com/group/google-appengine.
> To view this discussion on the web visit
> 

[google-appengine] Max 10,000 file limit is not suitable for modern full featured wordpress site or any PHP app

[Shaharia Azam]

Hello Everyone,
I know this is a common questions but actually this is now becoming more 
and more strange to me day by day. Why Google still feels about the hard 
limit related to max 10,000 file? If I want to install Wordpress latest 
version with any premium themes, few e-commerce related mandatory plugins 
then easily from the beginning of my development this would cross 10,000 
files. 

We are a web solution provider company and we are facing few very hard 
questions that is forbidding us to suggest GCP to our client's for their 
needs.

1. Advance & Full featured E-Commerce site powered by Wordpress due to 
10,000 file limit issue.
2. SMTP outgoing issue due to block of Port 25. Even our own cPanel server 
is hosted on AWS for that. Rest of our servers that doesn't need email 
communication are on GCP.

Does Google think that it is irrelevant? Even from the quota request page, 
this file limit quota can't be increased. In this case, not only us but 
also lots of people are going away from using GCP and specially Google App 
Engine (our use case depends on it). So I want to hear something from any 
internal team members about this. Is there any plan in future to remove 
this limit or increase this limit or you are suggesting us to go away from 
App engine to somewhere else?

- @shaharia

-- 
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-appengine@googlegroups.com.
Visit this group at https://groups.google.com/group/google-appengine.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/google-appengine/b0b16c5c-7f22-4db8-847d-e93efd5cb0ef%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.