When I add the secure: always parameter in app.yaml, I am still not redirected to a https. Https works when I type it in manually, and I'm testing this on the live server, but it treats the website as though secure: always isn't there.
I eventually just tried to map it to all the handlers in the yaml file, but it still has no effect.
application: appname
version: 1
runtime: python27
api_version: 1
threadsafe: yes
handlers:
- url: /favicon\.ico
static_files: favicon.ico
upload: favicon\.ico
secure: always
- url: /css
static_dir: css
secure: always
- url: /fonts
static_dir: fonts
secure: always
- url: /js
static_dir: js
secure: always
- url: /img
static_dir: img
secure: always
- url: .*
script: main.app
secure: always
libraries:
- name: webapp2
version: "2.5.2"
- name: jinja2
version: "2.6"
error_handlers:
- file: default_error.html
Related
Following error as shown in screen-shot,occurs when i try to run my helloworld.py script in Google App engine from terminal.
#My Operating system:Ubuntu.14.#
And Here is my file app.yaml.
application: #My project Id.
version: 1
runtime: python27
threadsafe: true
api_version: 1
handlers:
- url: /static
static_dir: static
- url: /
static_files: static/index.html
upload: static/index\.html
secure: always
- url: /_ah/spi/.*
script: helloworld_api.app
libraries:
- name: endpoints
version: 1.0
The Problem is that i can't deploy my code on local machine.
Any helps would be Appreciated.Thanks :)
I had check Online Yaml parser and it shows its Valid too.
You're missing the libraries line, the endpoints library are actually interpreted as part of the handlers list, which is incorrect.
Should look like this:
...
- url: /_ah/spi/.*
script: helloworld_api.app
libraries:
- name: endpoints
version: 1.0
I have this app.yaml:
application: xyz
version: 1
runtime: python27
api_version: 1
threadsafe: true
handlers:
- url: /static
static_dir: static
- url: /admin/.*
script: admin.app
login: admin
- url: /.*
script: main.app
libraries:
- name: webapp2
version: latest
- name: jinja2
version: latest
when I access /admin/, both the dev server and appengine display the contents without asking for authentication. What gives?
I've run into this before. Try clearing your cookies. Clearing the cookies also helps if you accidentally forgot to check "log in as administrator" when the dev server prompts you for the fake login info.
I'm using the following yaml configuration:
application: xxxxxxxx
version: 1
runtime: python27
api_version: 1
threadsafe: true
handlers:
- url: /bootstrap
static_dir: static/bootstrap
- url: /fonts
static_dir: static/fonts
- url: /js
static_dir: static/js
- url: /images
static_dir: static/images
- url: /css
static_dir: static/css
- url: /favicon\.ico
static_files: ./static/favicon.ico
upload: ./static/favicon\.ico
- url: /.*
script: main.app
libraries:
- name: django
version: "1.3"
And my folder structure is like this:
\
....static
..........bootstrap
...................css
...................js
...................img
..........css
..........fonts
..........images
..........js
In the development environment it works fine (using latest version available), but when I deploy the app it doesn't. I know the filenames are case sensitive on gae, but I've already checked that.
What else can be wrong?
Please Help.
Thanks
As stupid it may seems but removing the project from GAE Launcher and adding it back again and re-deploy it solved the issue.
I am developing a web app in app engine python, I cant find GET /favicon.ico in console when I execute it in chrome or IE. Whereas there is no issue with firefox or safari, my favicon.ico is displayed in it.
here is my handlers in app.yaml:
handlers:
- url: /favicon.ico
static_files: favicon.ico
upload: favicon.ico
- url: /sitemap.xml
static_files: sitemap.xml
upload: sitemap.xml
- url: /robots.txt
static_files: robots.txt
upload: robots.txt
- url: /static
static_dir: static
- url: .*
script: main.app
There is no 404 error for favicon, /facivon.ico not getting executed in chrome , IE.
You could try
- url: /favicon\.ico
mime_type: image/vnd.microsoft.icon
static_files: static/favicon.ico
upload: static/favicon.ico
I am using flask and the python 2.7 GAE SDK. I am trying to include an interactive shell, in my app.
I am trying to include the following interactive python shell in my app, so that I can interact with the GAE API while development - http://code.google.com/p/google-app-engine-samples/source/browse/trunk/shell/
As instructed I have copied the static/ and templates/ folders, and shell.py to the root of my app.
I have also added the url route ONLY to my app.yaml (shell)-
application: myflaskonappengineapp
version: 1
runtime: python27
api_version: 1
threadsafe: false
default_expiration: "5d"
builtins:
- appstats: on
- admin_redirect: on
- deferred: on
- remote_api: on
libraries:
- name: jinja2
version: "2.6"
- name: markupsafe
version: "0.15"
- name: lxml
version: "2.3"
- name: numpy
version: "1.6.1"
- name: PIL
version: "1.1.7"
- name: pycrypto
version: "2.3"
- name: setuptools
version: "0.6c11"
- name: webapp2
version: "2.3"
- name: webob
version: "1.1.1"
- name: yaml
version: "3.10"
inbound_services:
- warmup
handlers:
- url: /favicon.ico
static_files: application/static/img/favicon.ico
upload: application/static/img/favicon.ico
- url: /robots.txt
static_files: application/static/robots.txt
upload: application/static/robots.txt
- url: /_gae_mini_profiler/static
static_dir: packages/flaskext/gae_mini_profiler/static
- url: /static
static_dir: application/static
#interactive shell
- url: /shell
script: shell.py
- url: /remote_api
script: /opt/google_appengine/google/appengine/ext/remote_api/handler.py
- url: .*
script: application.app
However when I try to access the url /shell, I get a 404 error ? Do I need to configure flask also for routing ? Why is flask handling this url instead of shell.py?
You need to modify the shell.py to handle the URL '/shell' as well as app.yaml.
In particular, you need to edit the line 303 of the shell.py.
from
[('/', FrontPageHandler),
to
[('/shell', FrontPageHandler),
You also need to update your app.yaml like(add wildcard):
- url: /shell.*
script: shell.py
Please consider adding login:admin to the shell handler, otherwise you will open up the shell capability to everyone in the world.