[google-appengine] CSR (Certificate Signing Request)
Hi - I've been having a really tough time getting a CSR for my custom domain that I have running with google app engine. Is there anyone who can tell me how to get a CSR for my domain? I am trying to upgrade my site to SSL and my Certificate Authority (CA is Comodo) needs me to give them a CSR in order to set everything up. How can I get a CSR from google or what is the process for maybe being able to create one myself? I originally bought my domain through Godaddy, but I'm not hosting it through Godaddy, I'm hosting it through the App Engine. Any help would be much appreciated! Thanks! -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/28478eb0-f92f-4c60-b697-d9cbb10d6c9a%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Call to URLFetch failed with application error 5 for url x
I would increase the timeout http://stackoverflow.com/a/18927990/3877822for
the url_fetch. If that does not work I would recommend posting on
StackOverflow
http://stackoverflow.com/questions/tagged/google-app-engine+php. You will
have a better chance of finding someone who has had a similar issue. If you
can prove it's a bug with the platform posting on the PIT
https://code.google.com/p/googleappengine/issues/list with a working
sample project would help fix the issue.
On Thursday, June 25, 2015 at 5:26:46 AM UTC-4, Flav Ible wrote:
*Background:*
I am using google app engine and am having a weird bug in my site crawler.
I have a backend that will automatically crawl a site every night. This is
instigated by a task pushed to a pushQueue due to time limits in php.
*Problem:*
When I manually run the script that creates the task, the task completes
as expected with no errors. However when cron launches the task I get the
following error.
Call to URLFetch failed with application error 5 for url x
Code:
function url_get_contents ($Url) {
global $retry;
try {
if (!function_exists('curl_init')){
die('CURL is not installed!');
}
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $Url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$output = curl_exec($ch);
curl_close($ch);
return $output;
} catch (Exception $e) {
syslog(LOG_INFO, 'Caught exception: ', $e-getMessage());
if($retry 0){
$retry -= 1;
return url_get_contents($Url);
}
else{
return null;
}
}}
Thanks to syslog I can see that the $url is fine which is driving me crazy
as it works when the exact same script is launched manually not through
cron.
How can I fix this?
Thanks in advance.
--
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/7f680dfe-5db1-4c12-a087-e338b9d3c6ee%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[google-appengine] deferred PermanentTaskFailure: __new__() takes exactly 4 arguments (due to DateTimePropety?) and How to override deferred.TaskHandler?
I've posted this question on SO http://stackoverflow.com/q/31005704/27826 a couple of days ago, and updated it with a few details since then. Essentially, I have a deferred task that leads to the error in the subject, which I suspect to come out of the call to unpickle the task request. I need to find more details about the failure, but have not found a way yet... maybe I should override the deferred.TaskHandler (but how to do that?) Thank you in advance for your time. -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/7eb95d25-2848-45f1-be51-3f8ebdb94437%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: high latency in urlfetch when calling an external API with google app engine
Dear Nick,
Thank you for your response. We measured the latency as you suggested and
the time is almost the same. The instance is in Europe and we are doing
tests from Madrid and from London.
Here is the problem we see. When we call to the API from a normal computer
it takes around 300ms, however when we call it from Google's compute engine
the trace is 3 or 4 times that. We don't understand why.
Is Google doing some internal operation that increases the request time?
are we doing something wrong?
Thanks
On 24 June 2015 at 20:00, Nick (Cloud Platform Support) pay...@google.com
wrote:
Hey ssmcookiemonster,
When debugging latency of a request, it's best to only surround the
request action itself with timing code, so you should profile the time to
execute the following two lines only:
FutureHTTPResponse future = fetcher.fetchAsync(url);
HTTPResponse responseHttp = future.get();
This will minimize the impact of memory-management, object-creation,
string-buffering, etc., and tend to show a more accurate measure of network
latency.
Another way to get insight into the problem is to ping / traceroute / mtr
the target of your request from various locations. You might want to run
these diagnostic tools from:
* your local development box
* a compute-engine instance in the same region as your app (US or EU)
* other locations around the world
This will allow you get a handle on how traffic will be routed to the
endpoint you're attempting to reach, and the relative latencies from
different locations.
You may also want to run Url Fetch requests to locations that are closer
to your app and/or development box and see how latency is affected.
Finally, you can install AppStats (Java
https://cloud.google.com/appengine/docs/java/tools/appstats | Python
https://cloud.google.com/appengine/docs/python/tools/appstats) on your
app to see the statistics around UrlFetch calls your app makes.
I hope this information has provided a helpful guide to debugging latency
with Url Fetch.
On Wednesday, June 24, 2015 at 4:23:23 AM UTC-4,
ssmcookiemons...@gmail.com wrote:
We have a Java application that make use of urlfetch calling an external
api. We are having issues with the request time. When we do a request in a
local environment we have a mean time of 300ms, however in production we
have times of 1s or 1.4s.
This is the code we are using:
Calendar start = Calendar.getInstance();
try {
URLFetchService fetcher =
URLFetchServiceFactory.getURLFetchService();
URL url = new URL( String.format( API_URL, productsIds ) );
FutureHTTPResponse future = fetcher.fetchAsync(url);
HTTPResponse responseHttp = future.get();
byte[] content = responseHttp.getContent();
response = new String(content);
System.out.println(request time : +
(Calendar.getInstance().getTimeInMillis() - start.getTimeInMillis() ) );
} catch ( Exception e ) {
LOGGER.log( Level.SEVERE, Error calling api : + e.getMessage() );
}
Is Google doing any kind of validation that produces this time increase?
Is there a way to reduce the request time?
Thank you very much
--
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/ryYsvyEily4/unsubscribe
.
To unsubscribe from this group and all its topics, 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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/3447916e-079b-4186-be6a-7a84fa99f1ea%40googlegroups.com
https://groups.google.com/d/msgid/google-appengine/3447916e-079b-4186-be6a-7a84fa99f1ea%40googlegroups.com?utm_medium=emailutm_source=footer
.
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/CADJ9T2VK36f99-7F4_CmE1-BUrEof4m7FL_xSm_arKpbkaEp6w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: creating a database instance independent of any project .
Hi there! Unfortunately, you cannot currently create a CloudSQL instance separate from a project itself, though what you can do is create a new instance https://cloud.google.com/sql/docs/create-instance within one of those projects, name it testdb as you mentioned, and work from there (so long as your application doesn't interact with it programmatically, it will be self-contained). You can also create a whole new project just for that instance if you really wanted, as it doesn't need an application tied to it, it just needs to exist. Cheers! On Wednesday, June 24, 2015 at 12:25:38 PM UTC-4, navn...@senspan.com wrote: I have 7 to 8 projects on google app engine, that my whole team works on , and now we have decided to create a test database, so their is a way to create this database instance , and name it testdb, because the only way i found out to create a instance is vis a application and going to sql cloud and then creating a new instance , but in that case the name if database instance is linked with project name . -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/e7976e2a-fcc4-4168-8b7f-ca557c590b4b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: How can I Serve SVG over SSL
Thank you Michael I will send you a private message asap with the app.yaml code. -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/13d6e4e8-51ea-4265-b0a4-98f0d6da2d7d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request
Hey everyone, There are a few possible causes for this error message. Could you please private message me the app-ids for the projects currently experiencing this issue so I can investigate further? Cheers! On Tuesday, June 23, 2015 at 5:01:42 AM UTC-4, PK wrote: For the past few days I see a lot of aborted calls with the message Request was aborted after waiting too long to attempt to service your request” It comes from deferred and other queued requests, I have not seen any change with interactive calls. Has anybody else noticed similar behavior? I use the scheduler with the default settings. Has anything changed? Thanks, PK p...@gae123.com -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/1b94b3a2-93e8-4f6d-8a85-4e3ea6e2c6a8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: deferred PermanentTaskFailure: __new__() takes exactly 4 arguments (due to DateTimePropety?) and How to override deferred.TaskHandler?
Hi Francesco, Unfortunately, cross-posting a specific technical issue to this forum isn't the way to proceed here. This forum is meant for more general discussion of the platform and services, rather than specific technical issues. You've already done everything you can do (short of do more debugging / studying yourself) in regards to getting this issue to the attention of people who might help by posting it to stackoverflow. If you'd like on-demand 1-on-1 technical support, you can always purchase a support package http://cloud.google.com/support. If you feel that your issue represents an issue on the platform (behaviour isn't as-documented), then you should open a public issue tracker thread https://code.google.com/p/googleappengine/issues/list with enough information to allow reproduction of the behaviour by the person reading your issue, preferably attaching a basic project which demonstrates the issue. I'll be doing my best to be active on that question, although of course this is no guarantee of a solution. So, at this point, I'd recommend returning to stackoverflow and working on the issue there. Have a nice day!. On Thursday, June 25, 2015 at 9:22:33 AM UTC-4, Francesco Rizzi wrote: I've posted this question on SO http://stackoverflow.com/q/31005704/27826 a couple of days ago, and updated it with a few details since then. Essentially, I have a deferred task that leads to the error in the subject, which I suspect to come out of the call to unpickle the task request. I need to find more details about the failure, but have not found a way yet... maybe I should override the deferred.TaskHandler (but how to do that?) Thank you in advance for your time. -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/dbb061a6-e999-4c41-8f11-524c9cf21cee%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: CSR (Certificate Signing Request)
Hey Brian, There are many tutorials out there on the web as to how you can use OpenSSL to create a CSR. Here's a document https://www.openssl.org/docs/HOWTO/certificates.txt produced by OpenSSL.org which is very good. You can also read about it on many sites by googling. Generally, this forum is meant for broad discussion of the platform and its services, not for 1-on-1 technical support or questions. This question might be better answered by consulting Google or maybe posting a question to stackoverflow or serverfault, although I'm sure there are already so many questions and answers on this same topic that to create a new one would invite duplicate flags. Overall, there's a wealth of information out there that I encourage you to access, and I wish you the best of luck in getting your certificate set up. As you go, make sure to consult the docs on Custom Domains and SSL https://cloud.google.com/appengine/docs/ssl. Best wishes, Nick On Thursday, June 25, 2015 at 3:56:32 PM UTC-4, Brian Ratkovich wrote: Hi - I've been having a really tough time getting a CSR for my custom domain that I have running with google app engine. Is there anyone who can tell me how to get a CSR for my domain? I am trying to upgrade my site to SSL and my Certificate Authority (CA is Comodo) needs me to give them a CSR in order to set everything up. How can I get a CSR from google or what is the process for maybe being able to create one myself? I originally bought my domain through Godaddy, but I'm not hosting it through Godaddy, I'm hosting it through the App Engine. Any help would be much appreciated! Thanks! -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/86e0c6fd-231d-426d-b1b1-25b4672f8de9%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Google App Engine version 1.9.23 SDK available
Greetings and salutations, Cheerfully I announce the next version of the App Engine SDK. https://cloud.google.com/appengine/downloads This includes: *All* - Memcache proxy allows you to use the standard memcache protocol and client libraries from your managed VM application. - Source location is logged for app logs in Java7 and Python27 for app_ids in the range “s~[np].*”; although this information does not appear in the logs viewer yet, it is available via the legacy logservice and when exported from Cloud Logging. -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/3046db46-8565-4947-a2ed-caca1cadb267%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: [google-appengine] Re: high latency in urlfetch when calling an external API with google app engine
Some further advice I can give you: If you check your App Engine logs, you can find that the two fields CPU milliseconds and Wall-clock milliseconds represent different metrics https://cloud.google.com/appengine/docs/python/logs/#Python_how_to_read_a_log. CPU milliseconds is a measure of how long your instance itself spent calculating the response, and Wall-clock milliseconds is the total amount of wall-clock time spent by App Engine serving the request. Keeping in mind that CPU milliseconds are measured against a baseline of 1.2 GHz intel x86 CPU (so if your instance is equipped with a processor that's a multiple of this, perform the appropriate scaling to get the true CPU milliseconds), you can find the difference between wall-clock time and CPU time to be the amount of time your instance was waiting on network requests to return (assuming you use synchronous HTTP fetches, which it appears you do since you immediately call .get(), which is a blocking call, on the HTTP Future). However, your timing code itself is also sufficient for this purpose, generally. It would be interesting to see if there's any difference between these two measures, since it could expose that there is other network latency other than the HTTP request you profiled directly with timing code, which could be affecting overall request latency. Overall, the infrastructure responsible for routing Url Fetch requests from your app is very, very different from the devserver SDK implementation of Url Fetch, which is basically just using your computer to send the request. Some discrepancies in timing are to be expected since Url Fetch in production is a much more robust system. However, if you're interested in further analyzing the timing further, realize that where your app is located, where the endpoint you're trying to reach is located, where your dev-box is located, can all influence the various timings. You say that you've run a test from a Compute Engine instance in the same region as your application (Europe). If you didn't already, I'd suggest running MTR https://en.wikipedia.org/wiki/MTR_(software)to see the exact path of your connection and the latency of the various hops. If the request takes 300ms to complete from your own computer, you should also run MTR to determine how much of that is network latency vs. processing on the actual endpoint you connect to. The latency on requests from the Compute Engine instance seems odd, and I'd be very interested to see the MTR output from that machine to the host you want to reach. So, these are some of my further thoughts on the analysis of network latency with regard to Url Fetch, Compute Engine, and global IP routing. Let me know if you have any further questions! On Thursday, June 25, 2015 at 10:44:29 AM UTC-4, Cookie Monster Samsamia wrote: Dear Nick, Thank you for your response. We measured the latency as you suggested and the time is almost the same. The instance is in Europe and we are doing tests from Madrid and from London. Here is the problem we see. When we call to the API from a normal computer it takes around 300ms, however when we call it from Google's compute engine the trace is 3 or 4 times that. We don't understand why. Is Google doing some internal operation that increases the request time? are we doing something wrong? Thanks On 24 June 2015 at 20:00, Nick (Cloud Platform Support) pay...@google.com wrote: Hey ssmcookiemonster, When debugging latency of a request, it's best to only surround the request action itself with timing code, so you should profile the time to execute the following two lines only: FutureHTTPResponse future = fetcher.fetchAsync(url); HTTPResponse responseHttp = future.get(); This will minimize the impact of memory-management, object-creation, string-buffering, etc., and tend to show a more accurate measure of network latency. Another way to get insight into the problem is to ping / traceroute / mtr the target of your request from various locations. You might want to run these diagnostic tools from: * your local development box * a compute-engine instance in the same region as your app (US or EU) * other locations around the world This will allow you get a handle on how traffic will be routed to the endpoint you're attempting to reach, and the relative latencies from different locations. You may also want to run Url Fetch requests to locations that are closer to your app and/or development box and see how latency is affected. Finally, you can install AppStats (Java https://cloud.google.com/appengine/docs/java/tools/appstats | Python https://cloud.google.com/appengine/docs/python/tools/appstats) on your app to see the statistics around UrlFetch calls your app makes. I hope this information has provided a helpful guide to debugging latency with Url Fetch. On Wednesday, June 24, 2015 at 4:23:23 AM UTC-4,
[google-appengine] Re: How to run a long task until it ends ?
As mentioned, this can sometimes occur if you begin exhausting instance memory. You could try to do one of the following actions to alleviate such a problem: - If your task processing contains a loop, on each iteration (or every N iterations, or even using time-based logic if you'd like), you can test the amount of memory usage and back off on processing / shift a portion of procession to another instance if you're getting too close to the limit. You could also use (for manual scaling instances), a background-thread https://cloud.google.com/appengine/docs/java/modules/#Java_Background_threads to monitor this. - Break the task into smaller portions and distribute them among instances which can handle the load - Determine whether it truly is memory exhausting causing the instances to spin down by combining your own profiling with the information available from the Developers Console logs view. - Inspect your code to determine where possible painful situations can occur for memory, where you're perhaps loading the entire contents of a large file into memory. With these methods, you'll be able to either narrow down how to fix your memory issue, or determine that the issue isn't memory exhaustion. I'm curious as to what you mean by calling ofy().clear() sometimes did not solve anything. Does this mean that it did seem to, at least somewhat, alleviate the problem? Also, yes you should be using the static import ofy() method as the docs describe, not holding onto any objects of type Objectify. Best wishes, Nick On Wednesday, June 24, 2015 at 4:54:19 PM UTC-4, nilsler...@gmail.com wrote: Thank you Chad Vincent for your answer. I added some logging, but it didn't gave me more relevant information. Everything is running fine until the unexplainable failure. Therefore, I guess that it is related to a memory issue. It retrieves data and caches until the memory is full and then crashes. I spent some time tonight reading the Objectify documentation. I came across this: https://code.google.com/p/objectify-appengine/wiki/BasicOperations#The_Session_Cache . It could really be related to my issue. Unfortunately calling ofy().clear() sometimes did not solve anything. Moreover, I read that assigning ObjectifyService.ofy() was a bad idea. But requesting ofy() directly each time I needed it did not help neither. Any other idea or suggestion is welcome. Thank you :) . G. Le mercredi 24 juin 2015 22:30:38 UTC+2, Chad Vincent a écrit : Then I would definitely add more logging so you can see what is and is not getting done before the instance bails. On Wednesday, June 24, 2015 at 1:48:07 AM UTC-5, nilsl...@gmail.com wrote: Thank you for answering me. Here is the only log I'm getting : /task/update-known-devices 500 151600ms 0kb AppEngine-Google; (+ http://code.google.com/appengine) module=default version=dev 1. 0.1.0.2 - - [23/Jun/2015:23:23:07 -0700] POST /task/update-known-devices HTTP/1.1 500 0 http://freemobile-netstat.appspot.com/cron/update-known-devices; AppEngine-Google; (+http://code.google.com/appengine) freemobile-netstat.appspot.com ms=151600 cpu_ms=3530 queue_name=update-queue task_name=81805458203132447311 exit_code=202 app_engine_release=1.9.22 trace_id=b86eb2915714ad73aae5f54bfbef746d instance=00c61b117c5b3b509e154cd4930e3af3083a8a68 https://appengine.google.com/instances?app_id=e~freemobile-netstatversion_id=dev.385229375500191200key=00c61b117c5b3b509e154cd4930e3af3083a8a68#00c61b117c5b3b509e154cd4930e3af3083a8a68 2. E2015-06-24 08:23:07.492 A problem was encountered with the process that handled this request, causing it to exit. This is likely to cause a new process to be used for the next request to your application. (Error code 202) This log appears for each retry (around 3 times per task). G. Le mercredi 24 juin 2015 01:00:49 UTC+2, Chad Vincent a écrit : What are you getting in your logs? Any uncaught exceptions? You might want to add some debug logging statements and lower the logging level for a while to see what is happening. You do get 10 minutes for queries from the TaskQueue, so it isn't a timeout issue. On Tuesday, June 23, 2015 at 1:31:59 PM UTC-5, nilsl...@gmail.com wrote: Hi everybody, I have a long task to run under my App Engine application with a lot of computing. But after a while running the task (~2 minutes), it stops and just retries. Obviously, my task restarts from the beginning and cannot end. I would like to configure App Engine to run the task until it is finished. I've heard about a 10 minutes limit for the tasks. I guess it should be enough if it didn't retries everytime. My source code is (hopefully) freely available here : https://github.com/gilbsgilbs/freemobilenetstat-gae . The two tasks under *src/main/java/org/pixmob/freemobile/netstat/gae/web/task* are
[google-appengine] Re: Starting Penetration testing on GAE
Hey Azher, Any app-level security tests are going to be fine: injection, CSRF, XSS, etc., will be fine to test, since we don't monitor or prevent this in any way. It's up to app developers to safeguard from these app-level vulnerabilities. However, when it comes to DOS, be aware that our infrastructure does actively prevent these, as you can read in the Security Whitepaper https://cloud.google.com/security/whitepaper: All traffic is routed through custom GFE (Google Front End) servers to detect and stop malicious requests and Distributed Denial of Service (DDoS) attacks. Conducting a (D)DOS attack, whether real or a test (they're ultimately identical in terms of network packets), will have the result of potentially rousing the infrastructure security systems from slumber, and might result in black-listing the IPs you used as your launchpad for the (D)DOS. Additionally, note that attempting to break out of the security sandbox is of course in violation of the Terms of Service https://cloud.google.com/terms/, and you'll want to take a look at that as well before proceeding. Do you have any further questions related to security and pen-testing? -- Nick On Thursday, June 25, 2015 at 5:15:08 AM UTC-4, Azher Uddin Farooqi wrote: Hi, We are starting penetration testing (for DOS, CSRF and XSS attacks etc.) on Google App Engine. Do you see any issues ? -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/16ce-dc04-455e-9638-9f4a07dca9dd%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: deferred PermanentTaskFailure: __new__() takes exactly 4 arguments (due to DateTimePropety?) and How to override deferred.TaskHandler?
I took a quick glance at your SO question now, it seemed too cryptic to me After having my own issues with deferred, I modified a custom one for myself, I haven't been using the default deferred for years At the time, the deferred lacked crucial features, especially with async operations, so I had to do this, 1-2 years later they added the features I requested The deferred logic is EXTREMELY simple and elegant, you should just inspect the deferred library code and modify it or understand it to suit your needs, it's probably 60 lines or something -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/e0e0a156-a98c-40d2-b715-6d202bfd0e06%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Re: Request was aborted after waiting too long to attempt to service your request
I also experienced these again recently, they are part of the rare appengine issue bursts, rarely things go wrong and deadline exceptions, transient errors and these errors arise, it's expected (at least I come to expect them) I used to experience these every day, but throttling my routines prevented them The sad truth is, appengine can't handle too much acceleration, bursting of tasks etc. - so throttling the routine that caused these errors will fix the issue - it's what I did, after reducing my taskqueue rates and buckets, the issue was gone -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/12fb4c3f-1945-4644-9925-0cf312927b63%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
[google-appengine] Call to URLFetch failed with application error 5 for url x
*Background:*
I am using google app engine and am having a weird bug in my site crawler.
I have a backend that will automatically crawl a site every night. This is
instigated by a task pushed to a pushQueue due to time limits in php.
*Problem:*
When I manually run the script that creates the task, the task completes as
expected with no errors. However when cron launches the task I get the
following error.
Call to URLFetch failed with application error 5 for url x
Code:
function url_get_contents ($Url) {
global $retry;
try {
if (!function_exists('curl_init')){
die('CURL is not installed!');
}
$ch = curl_init();
curl_setopt($ch, CURLOPT_URL, $Url);
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
$output = curl_exec($ch);
curl_close($ch);
return $output;
} catch (Exception $e) {
syslog(LOG_INFO, 'Caught exception: ', $e-getMessage());
if($retry 0){
$retry -= 1;
return url_get_contents($Url);
}
else{
return null;
}
}}
Thanks to syslog I can see that the $url is fine which is driving me crazy
as it works when the exact same script is launched manually not through
cron.
How can I fix this?
Thanks in advance.
--
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 http://groups.google.com/group/google-appengine.
To view this discussion on the web visit
https://groups.google.com/d/msgid/google-appengine/677e26b9-79b0-4de6-adff-585fb679fa9f%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[google-appengine] Starting Penetration testing on GAE
Hi, We are starting penetration testing (for DOS, CSRF and XSS attacks etc.) on Google App Engine. Do you see any issues ? -- 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 http://groups.google.com/group/google-appengine. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/24eaaca3-647b-4218-84bc-dc7615a93044%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
