Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

[timh]

Hi Kamran


I have changed the CNAME to be ghs.googlehosted.com. and that did sort out 
the problem

Thanks for your help.

Regards

Tim Hoffman


On Tuesday, September 19, 2017 at 7:46:08 AM UTC+8, Kamran (Google Cloud 
Support) wrote:
>
>
> Hello Tim,
>
> It looks like that CNAME record of your domain is not correctly 
> configured. Please login to your domain registrar and modify the CNAME 
> record of your domain to point to *ghs.googlehosted.com 
> .  *Right now I can see that it's configured 
> incorrectly pointing to ghs.google.com. 
>
> After updating the CNAME, it would take some time for DNS record to be 
> propagated and the managed security takes place.
>
> Sincerely,
>
>
> On Monday, September 18, 2017 at 7:04:07 PM UTC-4, timh wrote:
>>
>> Hi Lorne
>>
>> Here is the link  https://issuetracker.google.com/issues/65781183
>>
>> The DNS changed in cloud console on reverification, and our site is 
>> accessible using the name.
>>
>> So I don't have any evidence to suggest it didn't . 
>>
>> Regards
>>
>> Tim Hoffman 
>>
>>
>> On Tue, Sep 19, 2017 at 1:00 AM, 'Lorne Kligerman' via Google App Engine 
>>  wrote:
>>
>>> Tim, are you sure your DNS records have been updated?
>>> Could you send me a link to the public issue you logged with more 
>>> details?
>>> Thanks!
>>>
>>> On Sunday, September 17, 2017 at 8:22:02 AM UTC-7, Mike Hardy wrote:

 Likewise. I posted it here 
 .

 On Saturday, September 16, 2017 at 6:24:25 PM UTC-7, timh wrote:
>
> Hi
>
> Thanks have done so.
> Other than it not working there isn't much to report, there are no 
> error messages as such, just the forever spinning circle.
> The main bit of info will of course be the appid.
>
> Cheers
>
> T
>
>
> On Sunday, September 17, 2017 at 5:58:40 AM UTC+8, Kamran (Google 
> Cloud Support) wrote:
>>
>>
>> Hello Tim,
>>
>> I'd recommend filing an issue on Google Issue Tracker 
>>  include reproduction 
>> steps, the error messages that you receive or a redacted screenshot of 
>> the 
>> error, your Project ID and any other information that could help us to 
>> investigate this issue further.
>>
>>
>>
>> On Saturday, September 16, 2017 at 12:47:38 AM UTC-4, timh wrote:
>>>
>>> So I re-verified the same domain which appeared to work.
>>> It's details now look different but everything still working.
>>>
>>> I then "Enable Managed Security", and it started to show 
>>> "Google-managed, 
>>> auto-renewing " under SSL Security.
>>> However an hour later the adjacent spinning gif is still spinning, 
>>> have disabled and tried again to no avail.
>>>
>>> Not sure how to progress now.
>>>
>>> T 
>>>
>>>
>>> On Saturday, September 16, 2017 at 11:24:31 AM UTC+8, timh wrote:

 Hi

 Managed SSL - fantastic.

 However I have an existing domain mapped, (for many years) and you 
 don't seem to be able to add a certificate to this.

 Not sure what the strategy would be to resolve this without 
 potential downtime for the domain.

 The only thing would be drop the existing domain mapping and 
 re-add, but that will mean downtime for the service for that domain.

 Any ideas on how one might approach this without the potential 
 downtime ?

 Thanks

 Tim

>>> -- 
>>> You received this message because you are subscribed to a topic in the 
>>> Google Groups "Google App Engine" group.
>>> To unsubscribe from this topic, visit 
>>> https://groups.google.com/d/topic/google-appengine/_ErrNAHN3_4/unsubscribe
>>> .
>>> To unsubscribe from this group and all its topics, send an email to 
>>> google-appengi...@googlegroups.com .
>>> To post to this group, send email to google-a...@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/2b94783f-d540-4275-8b61-2c7928d34a83%40googlegroups.com
>>>  
>>> 
>>> .
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>
>>

-- 
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 

[google-appengine] Latest gradle plugin release fails with ExplodeWarTask.preserve() error

['Richard Perfect' via Google App Engine]

Hi,

This is my first day learning Google App-Engine, but I got stuck for a 
while on what looks to be a problem with the latest release of the Gradle 
plugin.

In the build.gradle example here 
;
 
It seems the 1.3.3 release (from a few days ago on Sep 19th) gives me the 
following error;


C:\Projects\App-Engine-Gradle-Hello>gradlew compileJava

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\Projects\App-Engine-Gradle-Hello\build.gradle' line: 23

* What went wrong:
A problem occurred evaluating root project 'App-Engine-Gradle-Hello'.
> 
com.google.cloud.tools.gradle.appengine.standard.ExplodeWarTask.preserve(Lorg/gradle/api/Action;)Lorg/gradle/api/tasks/Sync;

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or 
--debug option to get more log output.

BUILD FAILED



But when I downgrade to one of the earlier releases e.g. 1.3.2 I don't get 
this issue.

It turns out that I was using an older version of Gradle and it seems that 
there's a difference between 1.3.2 and 1.3.3 that now requires a Gradle 
version of 3.+ instead of 2.x

Updating my gradle wrapper version to 3.3 solved the problem.

gradle wrapper --gradle-version 3.3


Just posting in case this helps someone, and so hopefully Google search 
finds this post for someone else.

Complete stacktrace follows for search engine indexing.


C:\Projects\App-Engine-Gradle-Hello>
C:\Projects\App-Engine-Gradle-Hello>gradlew compileJava --stacktrace

FAILURE: Build failed with an exception.

* Where:
Build file 'C:\Projects\App-Engine-Gradle-Hello\build.gradle' line: 23

* What went wrong:
A problem occurred evaluating root project 'App-Engine-Gradle-Hello'.
> 
com.google.cloud.tools.gradle.appengine.standard.ExplodeWarTask.preserve(Lorg/gradle/api/Action;)Lorg/gradle/api/tasks/Sync;

* Try:
Run with --info or --debug option to get more log output.

* Exception is:
org.gradle.api.GradleScriptException: A problem occurred evaluating root 
project 'App-Engine-Gradle-Hello'.
at 
org.gradle.groovy.scripts.internal.DefaultScriptRunnerFactory$ScriptRunnerImpl.run(DefaultScriptRunnerFactory.java:93)
at 
org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl$2.run(DefaultScriptPluginFactory.java:177)
at 
org.gradle.configuration.ProjectScriptTarget.addConfiguration(ProjectScriptTarget.java:77)
at 
org.gradle.configuration.DefaultScriptPluginFactory$ScriptPluginImpl.apply(DefaultScriptPluginFactory.java:182)
at 
org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:38)
at 
org.gradle.configuration.project.BuildScriptProcessor.execute(BuildScriptProcessor.java:25)
at 
org.gradle.configuration.project.ConfigureActionsProjectEvaluator.evaluate(ConfigureActionsProjectEvaluator.java:34)
at 
org.gradle.configuration.project.LifecycleProjectEvaluator.evaluate(LifecycleProjectEvaluator.java:55)
at 
org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:540)
at 
org.gradle.api.internal.project.AbstractProject.evaluate(AbstractProject.java:93)
at 
org.gradle.execution.TaskPathProjectEvaluator.configureHierarchy(TaskPathProjectEvaluator.java:42)
at 
org.gradle.configuration.DefaultBuildConfigurer.configure(DefaultBuildConfigurer.java:35)
at 
org.gradle.initialization.DefaultGradleLauncher$2.run(DefaultGradleLauncher.java:124)
at org.gradle.internal.Factories$1.create(Factories.java:22)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:53)
at 
org.gradle.initialization.DefaultGradleLauncher.doBuildStages(DefaultGradleLauncher.java:121)
at 
org.gradle.initialization.DefaultGradleLauncher.access$200(DefaultGradleLauncher.java:32)
at 
org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:98)
at 
org.gradle.initialization.DefaultGradleLauncher$1.create(DefaultGradleLauncher.java:92)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:91)
at 
org.gradle.internal.progress.DefaultBuildOperationExecutor.run(DefaultBuildOperationExecutor.java:63)
at 
org.gradle.initialization.DefaultGradleLauncher.doBuild(DefaultGradleLauncher.java:92)
at 
org.gradle.initialization.DefaultGradleLauncher.run(DefaultGradleLauncher.java:83)
at 
org.gradle.launcher.exec.InProcessBuildActionExecuter$DefaultBuildController.run(InProcessBuildActionExecuter.java:99)
at 
org.gradle.tooling.internal.provider.ExecuteBuildActionRunner.run(ExecuteBuildActionRunner.java:28)
at 
org.gradle.launcher.exec.ChainingBuildActionRunner.run(ChainingBuildActionRunner.java:35)
at 

[google-appengine] Re: Google Cloud Endpoints v2 framework (python) in the SDK?

['Shivam(Google Cloud Support)' via Google App Engine]

I understand your concern but this is not a valid feature request and I’ll 
explain why. Cloud Endpoints is a concept which applies to many 
resources(such as Compute Engine, Container Engine etc.) and not just App 
Engine. You can find the list here 
. 

It helps you create, deploy, protect, monitor, analyze, and serve your APIs 
using the same infrastructure Google uses for its own APIs. You can use any 
language and framework to write an API, add an OpenAPI specification or 
gRPC API configuration, and Cloud Endpoints will monitor and protect your 
API. So it is like a general availability product.


On Friday, September 22, 2017 at 10:01:29 AM UTC-4, Ivo Bellin Salarin 
wrote:
>
> Hi all,
>
> May I ask you if the google cloud endpoints v2 will be available as part 
> of the appengine standard SDK? When do you think that it will be included?
>
> Reminder: today, we have to include it as a thirdparty library, and use 
> vendor.add in order to use it. This contributes to explose the 10k files 
> threshold for a appengine standard deploy.
>
> Thanks,
> Ivo
>

-- 
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/97eaea94-4cfd-4cb9-aa9a-4ba9aff60c29%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

['Lorne Kligerman' via Google App Engine]

Please send me your project id and domain that's having the issue privately
and we'll take a look.

On Fri, Sep 22, 2017 at 6:33 AM, Tapir  wrote:

>
>
> On Thursday, September 21, 2017 at 5:55:29 PM UTC-4, Lorne Kligerman wrote:
>>
>> Glad it kicked in!  If DNS entries aren't found, the system will
>> automatically retry, however it will back off and the retry is less
>> periodic the longer time passes.  Have you tried checking off only one
>> domain in the table?  Are the buttons still disabled then?
>>
>
> Yes, I only checked one domain, but the button is still disabled.
>
>
>>
>> On Thu, Sep 21, 2017 at 3:45 AM, Tapir  wrote:
>>
>>>
>>>
>>> On Wednesday, September 20, 2017 at 8:32:16 AM UTC-4, Tapir wrote:



 On Monday, September 18, 2017 at 7:54:13 PM UTC-4, Kamran (Google Cloud
 Support) wrote:
>
>
> No. Updating the CNAME to point to *ghs.googlehosted.com
>  *shouldn't interrupt your HTTP service.
>

 how long will it take effect after clicking the "Enable Managed
 Security" button?
 I changed all my cnames to ghs.googlehosted.com but it still doesn't
 work.
 There is a waiting circle always rotating beside the domain.

>>>
>>> The circle disappears now and the ssl takes effect now! Thanks!
>>>
>>>

 The "Enable Managed Security" button of one of my another app is even
 always disabled, even of I select the www.mydomain.com domain.

>>>
>>> But this button is still always disabled.
>>>
>>> BTW, is there a way to force a http connection to convert to https
>>> connection?
>>>
>>>


>
>
> On Monday, September 18, 2017 at 7:50:12 PM UTC-4, timh wrote:
>>
>> Ok
>>
>> The cname record  is what was there from the many years old mapping.
>>
>> I havent changed that as I was concerned we would then lose access to
>> the site.
>>
>> Ignoring the ssl security do you see it changing  causing a problem
>> for http
>>
>> Thanks
>>
>> Tim
>>
>> On 19 Sep. 2017 7:46 am, "'Kamran (Google Cloud Support)' via Google
>> App Engine"  wrote:
>>
>>
>> Hello Tim,
>>
>> It looks like that CNAME record of your domain is not correctly
>> configured. Please login to your domain registrar and modify the CNAME
>> record of your domain to point to *ghs.googlehosted.com
>> .  *Right now I can see that it's
>> configured incorrectly pointing to ghs.google.com.
>>
>> After updating the CNAME, it would take some time for DNS record to
>> be propagated and the managed security take place.
>>
>> Sincerely,
>>
>>
>> On Monday, September 18, 2017 at 7:04:07 PM UTC-4, timh wrote:
>>>
>>> Hi Lorne
>>>
>>> Here is the link  https://issuetracker.google.com/issues/65781183
>>>
>>> The DNS changed in cloud console on reverification, and our site is
>>> accessible using the name.
>>>
>>> So I don't have any evidence to suggest it didn't .
>>>
>>> Regards
>>>
>>> Tim Hoffman
>>>
>>>
>>> On Tue, Sep 19, 2017 at 1:00 AM, 'Lorne Kligerman' via Google App
>>> Engine  wrote:
>>>
 Tim, are you sure your DNS records have been updated?
 Could you send me a link to the public issue you logged with more
 details?
 Thanks!

 On Sunday, September 17, 2017 at 8:22:02 AM UTC-7, Mike Hardy wrote:
>
> Likewise. I posted it here
> .
>
> On Saturday, September 16, 2017 at 6:24:25 PM UTC-7, timh wrote:
>>
>> Hi
>>
>> Thanks have done so.
>> Other than it not working there isn't much to report, there are
>> no error messages as such, just the forever spinning circle.
>> The main bit of info will of course be the appid.
>>
>> Cheers
>>
>> T
>>
>>
>> On Sunday, September 17, 2017 at 5:58:40 AM UTC+8, Kamran (Google
>> Cloud Support) wrote:
>>>
>>>
>>> Hello Tim,
>>>
>>> I'd recommend filing an issue on Google Issue Tracker
>>>  include
>>> reproduction steps, the error messages that you receive or a 
>>> redacted
>>> screenshot of the error, your Project ID and any other information 
>>> that
>>> could help us to investigate this issue further.
>>>
>>>
>>>
>>> On Saturday, September 16, 2017 at 12:47:38 AM UTC-4, timh wrote:

 So I re-verified the same domain which appeared to work.
 It's details now look different but everything still working.

[google-appengine] Feedback on App Engine Task Queue

['Steren Giannini' via Google App Engine]

Dear App Engine users,

If you are using App Engine Task Queue, please take one minute to answer 
these three questions: https://goo.gl/forms/Eaag1Ftl8X8YKiht2 

Your feedback will help us build a better service.

Thanks,
Steren
Product Manager, Google Cloud Platform

-- 
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/5c3ef861-ef4a-432a-9903-9cf3fd4a94b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Java8 on standard: need to migrate off Endpoints v1?

[Charles Capps]

Hi Nico,

It's a straightforward process if you use the Jersey Servlet container, 
since GAE works well with any servlet-based technology. In the services we 
have already migrated to Jersey, we only need these 2 maven dependencies 
from Jersey (currently using version 2.25.1):


>   org.glassfish.jersey.containers
>   jersey-container-servlet-core
>   ${jersey.version}
> 
> 
>   org.glassfish.jersey.media
>   jersey-media-json-jackson
>   ${jersey.version}
> 


Then, in your web.xml, you can define a servlet like:

> 
> MyServiceApplication
> 
> org.glassfish.jersey.servlet.ServletContainer
> 
>   javax.ws.rs.Application
>   com.mycompany.jersey.MyServiceApplication
> 
> 1
>   


where the MyServiceApplication class extends the JAX-RS Application base 
class, for which you can find documentation 
at https://jersey.github.io/documentation/latest/index.html
 
Good luck migrating!

On Thursday, September 21, 2017 at 11:52:47 PM UTC-7, Nico Verwer wrote:
>
> Is there a guide on how to use Jersey on App Engine?
> I am still on Cloud Endpoints v1, and I am reluctant to migrate to v2 
> because it might be deprecated before I finish the migration. Jersey is 
> probably more stable and future-proof. And, as you indicate, it is faster 
> than GCE v2.
>

-- 
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/d4f6bd08-1895-4225-8e3d-8b3682a62938%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: Running Laravel 5.4 on Google App Engine

['Shivam(Google Cloud Support)' via Google App Engine]

Google Groups discussion forum is meant for open-ended discussions. This 
sounds like a technical support question which are best suited for 
Stackoverflow . Make 
sure to use valid tags. 

That said, this post 

 
may help in resolving the issue.


On Friday, September 22, 2017 at 10:01:31 AM UTC-4, Rick de Jong wrote:
>
> I proceed to run my Laravel 5.4-application on Google App Engine (GAE), 
> with the following *env_variables* in my *app.yaml*:
>
> APP_LOG_LEVEL: debug
> APP_LOG: syslog
> STORAGE_DIR: /tmp
> FILESYSTEM: gae
> CACHE_SERVICES_FILE: true
> CACHE_CONFIG_FILE: true
> CACHE_ROUTES_FILE: true
> CACHE_COMPILED_VIEWS: true
> BROADCAST_DRIVER: log
> CACHE_DRIVER: memcached
> SESSION_DRIVER: memcached
> QUEUE_DRIVER: gae
>
> I still get the error:
>
> The bootstrap/cache directory must be present and writable.
>
> What do I need to change to get my application working?
>
> Thanks, 
>
> Rick
>

-- 
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/5106a93c-a8cc-4acb-b9f3-d97887c97b43%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Re: how can I download or get ApiProxy package

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

Hello Gao, AppScale has no relation to App Engine so I cannot help you 
diagnose issue with their SDK. You should instead use AppScale's help and 
support resources or ask your question on Stack Overflow using the AppScale 
tag .

On Thursday, September 21, 2017 at 9:24:08 PM UTC-4, 高科 wrote:
>
> Hello,  I run an application  at Appscale （the Appscale appengineSDK 
> version is 1.8.4， lower then GAE）,it catch an exception show below:
> Sep 21, 2017 5:20:13 AM com.google.apphosting.utils.jetty.JettyLogger warn
> WARNING: Error for /uk/iapProcessPurchaseV2
> java.lang.NoSuchMethodError: 
> com.google.apphosting.api.ApiProxy$Environment.getModuleId()Ljava/lang/String;
> at 
> com.google.appengine.api.modules.ModulesServiceImpl.getCurrentModule(ModulesServiceImpl.java:60)
> at 
> com.madfinger.framework.utils.ExceptionUtils.RecordException(ExceptionUtils.java:151)
> at 
> com.madfinger.iap.v2.commands.CmdIAPProcessPurchaseBase.ProcessAuthorized(CmdIAPProcessPurchaseBase.java:83)
> at 
> com.madfinger.framework.servlet.ServletPrimary.HandleCommand(ServletPrimary.java:373)
> at 
> com.madfinger.framework.servlet.ServletPrimary.doPostInternal(ServletPrimary.java:153)
> at 
> com.madfinger.framework.servlet.ServletPrimary.DoPost(ServletPrimary.java:77)
> at com.madfinger.framework.servlet.ServletBase.doPost(ServletBase.java:97)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:637)
> at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
> at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:511)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1166)
> at 
> com.googlecode.objectify.ObjectifyFilter.doFilter(ObjectifyFilter.java:48)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at 
> com.google.appengine.api.socket.dev.DevSocketFilter.doFilter(DevSocketFilter.java:74)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at 
> com.google.appengine.tools.development.ResponseRewriterFilter.doFilter(ResponseRewriterFilter.java:123)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at 
> com.google.appengine.tools.development.HeaderVerificationFilter.doFilter(HeaderVerificationFilter.java:34)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at 
> com.google.appengine.api.blobstore.dev.ServeBlobFilter.doFilter(ServeBlobFilter.java:63)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at 
> com.google.apphosting.utils.servlet.TransactionCleanupFilter.doFilter(TransactionCleanupFilter.java:48)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at 
> com.google.appengine.tools.development.StaticFileFilter.doFilter(StaticFileFilter.java:125)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at 
> com.google.appengine.tools.development.DevAppServerModulesFilter.doDirectRequest(DevAppServerModulesFilter.java:368)
> at 
> com.google.appengine.tools.development.DevAppServerModulesFilter.doDirectModuleRequest(DevAppServerModulesFilter.java:351)
> at 
> com.google.appengine.tools.development.DevAppServerModulesFilter.doFilter(DevAppServerModulesFilter.java:116)
> at 
> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1157)
> at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:388)
> at 
> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216)
> at org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:182)
> at org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:765)
> at org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:418)
> at 
> com.google.appengine.tools.development.DevAppEngineWebAppContext.handle(DevAppEngineWebAppContext.java:97)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at 
> com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handleImpl(Unknown
>  
> Source)
> at 
> com.google.appengine.tools.development.JettyContainerService$ApiProxyHandler.handle(Unknown
>  
> Source)
> at org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:152)
> at org.mortbay.jetty.Server.handle(Server.java:326)
>
>
> I have replaced appengine sdk version 1.8.4 to 1.9.48, this msg tell me no 
> such Method,I want to see where is the ApiProxy package? anyone can give me 
> a git or svn to let me know.
> Best regards!
> Gao
>

-- 
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] Running Laravel 5.4 on Google App Engine

[Rick de Jong]

I proceed to run my Laravel 5.4-application on Google App Engine (GAE), 
with the following *env_variables* in my *app.yaml*:

APP_LOG_LEVEL: debug
APP_LOG: syslog
STORAGE_DIR: /tmp
FILESYSTEM: gae
CACHE_SERVICES_FILE: true
CACHE_CONFIG_FILE: true
CACHE_ROUTES_FILE: true
CACHE_COMPILED_VIEWS: true
BROADCAST_DRIVER: log
CACHE_DRIVER: memcached
SESSION_DRIVER: memcached
QUEUE_DRIVER: gae

I still get the error:

The bootstrap/cache directory must be present and writable.

What do I need to change to get my application working?

Thanks, 

Rick

-- 
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/9b9d0cfd-9556-4013-966a-173f39b3b097%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[google-appengine] Google Cloud Endpoints v2 framework (python) in the SDK?

[Ivo Bellin Salarin]

Hi all,

May I ask you if the google cloud endpoints v2 will be available as part of
the appengine standard SDK? When do you think that it will be included?

Reminder: today, we have to include it as a thirdparty library, and use
vendor.add in order to use it. This contributes to explose the 10k files
threshold for a appengine standard deploy.

Thanks,
Ivo

-- 
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/CAPc4eF-5kcqmCcFGSKf8-n2_D_y2Jib3see5Ff%2B_dH9VARo9mw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

[Tapir]

On Thursday, September 21, 2017 at 6:01:07 PM UTC-4, Kamran (Google Cloud 
Support) wrote:
>
> Tapir, 
>
> You can use "secure" handlers subelement to automatically redirect HTTP 
> requests to the HTTPS URL with the same path. For more information on 
> this visit this article 
> .
>

Thanks!
 

>
>
> On Thursday, September 21, 2017 at 6:45:56 AM UTC-4, Tapir wrote:
>>
>>
>>
>> On Wednesday, September 20, 2017 at 8:32:16 AM UTC-4, Tapir wrote:
>>>
>>>
>>>
>>> On Monday, September 18, 2017 at 7:54:13 PM UTC-4, Kamran (Google Cloud 
>>> Support) wrote:


 No. Updating the CNAME to point to *ghs.googlehosted.com 
  *shouldn't interrupt your HTTP service.

>>>
>>> how long will it take effect after clicking the "Enable Managed 
>>> Security" button?
>>> I changed all my cnames to ghs.googlehosted.com but it still doesn't 
>>> work.
>>> There is a waiting circle always rotating beside the domain.
>>>
>>
>> The circle disappears now and the ssl takes effect now! Thanks!
>>  
>>
>>>
>>> The "Enable Managed Security" button of one of my another app is even 
>>> always disabled, even of I select the www.mydomain.com domain.
>>>
>>
>> But this button is still always disabled.
>>
>> BTW, is there a way to force a http connection to convert to https 
>> connection?
>>  
>>
>>>  
>>>
  

 On Monday, September 18, 2017 at 7:50:12 PM UTC-4, timh wrote:
>
> Ok
>
> The cname record  is what was there from the many years old mapping.
>
> I havent changed that as I was concerned we would then lose access to 
> the site.
>
> Ignoring the ssl security do you see it changing  causing a problem 
> for http
>
> Thanks
>
> Tim
>
> On 19 Sep. 2017 7:46 am, "'Kamran (Google Cloud Support)' via Google 
> App Engine"  wrote:
>
>
> Hello Tim,
>
> It looks like that CNAME record of your domain is not correctly 
> configured. Please login to your domain registrar and modify the CNAME 
> record of your domain to point to *ghs.googlehosted.com 
> .  *Right now I can see that it's 
> configured incorrectly pointing to ghs.google.com. 
>
> After updating the CNAME, it would take some time for DNS record to be 
> propagated and the managed security take place.
>
> Sincerely,
>
>
> On Monday, September 18, 2017 at 7:04:07 PM UTC-4, timh wrote:
>>
>> Hi Lorne
>>
>> Here is the link  https://issuetracker.google.com/issues/65781183
>>
>> The DNS changed in cloud console on reverification, and our site is 
>> accessible using the name.
>>
>> So I don't have any evidence to suggest it didn't . 
>>
>> Regards
>>
>> Tim Hoffman 
>>
>>
>> On Tue, Sep 19, 2017 at 1:00 AM, 'Lorne Kligerman' via Google App 
>> Engine  wrote:
>>
>>> Tim, are you sure your DNS records have been updated?
>>> Could you send me a link to the public issue you logged with more 
>>> details?
>>> Thanks!
>>>
>>> On Sunday, September 17, 2017 at 8:22:02 AM UTC-7, Mike Hardy wrote:

 Likewise. I posted it here 
 .

 On Saturday, September 16, 2017 at 6:24:25 PM UTC-7, timh wrote:
>
> Hi
>
> Thanks have done so.
> Other than it not working there isn't much to report, there are no 
> error messages as such, just the forever spinning circle.
> The main bit of info will of course be the appid.
>
> Cheers
>
> T
>
>
> On Sunday, September 17, 2017 at 5:58:40 AM UTC+8, Kamran (Google 
> Cloud Support) wrote:
>>
>>
>> Hello Tim,
>>
>> I'd recommend filing an issue on Google Issue Tracker 
>>  include 
>> reproduction steps, the error messages that you receive or a 
>> redacted 
>> screenshot of the error, your Project ID and any other information 
>> that 
>> could help us to investigate this issue further.
>>
>>
>>
>> On Saturday, September 16, 2017 at 12:47:38 AM UTC-4, timh wrote:
>>>
>>> So I re-verified the same domain which appeared to work.
>>> It's details now look different but everything still working.
>>>
>>> I then "Enable Managed Security", and it started to show 
>>> "Google-managed, 
>>> auto-renewing " under SSL Security.
>>> However an hour later the adjacent spinning gif is still 
>>> spinning, have disabled and tried again to no avail.
>>>
>>> Not sure how to progress 

Re: [google-appengine] Re: ? How to implement managed SSL for a pre-existing domain mapping.

[Tapir]

On Thursday, September 21, 2017 at 5:55:29 PM UTC-4, Lorne Kligerman wrote:
>
> Glad it kicked in!  If DNS entries aren't found, the system will 
> automatically retry, however it will back off and the retry is less 
> periodic the longer time passes.  Have you tried checking off only one 
> domain in the table?  Are the buttons still disabled then?
>

Yes, I only checked one domain, but the button is still disabled.
 

>
> On Thu, Sep 21, 2017 at 3:45 AM, Tapir  
> wrote:
>
>>
>>
>> On Wednesday, September 20, 2017 at 8:32:16 AM UTC-4, Tapir wrote:
>>>
>>>
>>>
>>> On Monday, September 18, 2017 at 7:54:13 PM UTC-4, Kamran (Google Cloud 
>>> Support) wrote:


 No. Updating the CNAME to point to *ghs.googlehosted.com 
  *shouldn't interrupt your HTTP service.

>>>
>>> how long will it take effect after clicking the "Enable Managed 
>>> Security" button?
>>> I changed all my cnames to ghs.googlehosted.com but it still doesn't 
>>> work.
>>> There is a waiting circle always rotating beside the domain.
>>>
>>
>> The circle disappears now and the ssl takes effect now! Thanks!
>>  
>>
>>>
>>> The "Enable Managed Security" button of one of my another app is even 
>>> always disabled, even of I select the www.mydomain.com domain.
>>>
>>
>> But this button is still always disabled.
>>
>> BTW, is there a way to force a http connection to convert to https 
>> connection?
>>  
>>
>>>  
>>>
  

 On Monday, September 18, 2017 at 7:50:12 PM UTC-4, timh wrote:
>
> Ok
>
> The cname record  is what was there from the many years old mapping.
>
> I havent changed that as I was concerned we would then lose access to 
> the site.
>
> Ignoring the ssl security do you see it changing  causing a problem 
> for http
>
> Thanks
>
> Tim
>
> On 19 Sep. 2017 7:46 am, "'Kamran (Google Cloud Support)' via Google 
> App Engine"  wrote:
>
>
> Hello Tim,
>
> It looks like that CNAME record of your domain is not correctly 
> configured. Please login to your domain registrar and modify the CNAME 
> record of your domain to point to *ghs.googlehosted.com 
> .  *Right now I can see that it's 
> configured incorrectly pointing to ghs.google.com. 
>
> After updating the CNAME, it would take some time for DNS record to be 
> propagated and the managed security take place.
>
> Sincerely,
>
>
> On Monday, September 18, 2017 at 7:04:07 PM UTC-4, timh wrote:
>>
>> Hi Lorne
>>
>> Here is the link  https://issuetracker.google.com/issues/65781183
>>
>> The DNS changed in cloud console on reverification, and our site is 
>> accessible using the name.
>>
>> So I don't have any evidence to suggest it didn't . 
>>
>> Regards
>>
>> Tim Hoffman 
>>
>>
>> On Tue, Sep 19, 2017 at 1:00 AM, 'Lorne Kligerman' via Google App 
>> Engine  wrote:
>>
>>> Tim, are you sure your DNS records have been updated?
>>> Could you send me a link to the public issue you logged with more 
>>> details?
>>> Thanks!
>>>
>>> On Sunday, September 17, 2017 at 8:22:02 AM UTC-7, Mike Hardy wrote:

 Likewise. I posted it here 
 .

 On Saturday, September 16, 2017 at 6:24:25 PM UTC-7, timh wrote:
>
> Hi
>
> Thanks have done so.
> Other than it not working there isn't much to report, there are no 
> error messages as such, just the forever spinning circle.
> The main bit of info will of course be the appid.
>
> Cheers
>
> T
>
>
> On Sunday, September 17, 2017 at 5:58:40 AM UTC+8, Kamran (Google 
> Cloud Support) wrote:
>>
>>
>> Hello Tim,
>>
>> I'd recommend filing an issue on Google Issue Tracker 
>>  include 
>> reproduction steps, the error messages that you receive or a 
>> redacted 
>> screenshot of the error, your Project ID and any other information 
>> that 
>> could help us to investigate this issue further.
>>
>>
>>
>> On Saturday, September 16, 2017 at 12:47:38 AM UTC-4, timh wrote:
>>>
>>> So I re-verified the same domain which appeared to work.
>>> It's details now look different but everything still working.
>>>
>>> I then "Enable Managed Security", and it started to show 
>>> "Google-managed, 
>>> auto-renewing " under SSL Security.
>>> However an hour later the adjacent spinning gif is still 
>>> spinning, have disabled and tried again to no 

Re: [google-appengine] Java8 on standard: need to migrate off Endpoints v1?

[Nico Verwer]

Is there a guide on how to use Jersey on App Engine?
I am still on Cloud Endpoints v1, and I am reluctant to migrate to v2 
because it might be deprecated before I finish the migration. Jersey is 
probably more stable and future-proof. And, as you indicate, it is faster 
than GCE v2.

-- 
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/263a0556-c783-4333-a366-f35df4acfe6b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.