Flask Documentation 0.9Dev 2015 06 09

Total Page:16

File Type:pdf, Size:1020Kb

Flask Documentation 0.9Dev 2015 06 09 Flask Documentation 0.9dev 2015 06 09 Contents I User’s Guide1 1 Foreword3 1.1 What does “micro” mean?...........................3 1.2 Configuration and Conventions.......................3 1.3 Growing with Flask..............................4 2 Foreword for Experienced Programmers5 2.1 Thread-Locals in Flask.............................5 2.2 Develop for the Web with Caution......................5 2.3 The Status of Python 3.............................6 3 Installation7 3.1 virtualenv....................................7 3.2 System-Wide Installation...........................8 3.3 Living on the Edge...............................9 3.4 pip and distribute on Windows........................9 4 Quickstart 11 4.1 A Minimal Application............................ 11 4.2 Debug Mode.................................. 12 4.3 Routing..................................... 13 4.4 Static Files.................................... 17 4.5 Rendering Templates.............................. 17 4.6 Accessing Request Data............................ 19 4.7 Redirects and Errors.............................. 22 4.8 About Responses................................ 23 4.9 Sessions..................................... 24 4.10 Message Flashing................................ 25 4.11 Logging..................................... 25 4.12 Hooking in WSGI Middlewares....................... 26 4.13 Deploying to a Web Server.......................... 26 i 5 Tutorial 27 5.1 Introducing Flaskr............................... 27 5.2 Step 0: Creating The Folders......................... 28 5.3 Step 1: Database Schema........................... 29 5.4 Step 2: Application Setup Code........................ 29 5.5 Step 3: Creating The Database........................ 31 5.6 Step 4: Request Database Connections.................... 32 5.7 Step 5: The View Functions.......................... 33 5.8 Step 6: The Templates............................. 34 5.9 Step 7: Adding Style.............................. 36 5.10 Bonus: Testing the Application........................ 37 6 Templates 39 6.1 Jinja Setup.................................... 39 6.2 Standard Context................................ 39 6.3 Standard Filters................................. 40 6.4 Controlling Autoescaping........................... 41 6.5 Registering Filters............................... 41 6.6 Context Processors............................... 42 7 Testing Flask Applications 43 7.1 The Application................................ 43 7.2 The Testing Skeleton.............................. 43 7.3 The First Test.................................. 44 7.4 Logging In and Out.............................. 45 7.5 Test Adding Messages............................. 46 7.6 Other Testing Tricks.............................. 46 7.7 Keeping the Context Around......................... 47 7.8 Accessing and Modifying Sessions...................... 48 8 Logging Application Errors 49 8.1 Error Mails................................... 49 8.2 Logging to a File................................ 50 8.3 Controlling the Log Format.......................... 51 8.4 Other Libraries................................. 52 9 Debugging Application Errors 55 9.1 When in Doubt, Run Manually........................ 55 9.2 Working with Debuggers........................... 55 10 Configuration Handling 57 10.1 Configuration Basics.............................. 57 10.2 Builtin Configuration Values......................... 58 10.3 Configuring from Files............................. 60 10.4 Configuration Best Practices......................... 61 10.5 Development / Production.......................... 61 10.6 Instance Folders................................ 62 11 Signals 65 ii 11.1 Subscribing to Signals............................. 65 11.2 Creating Signals................................ 67 11.3 Sending Signals................................. 67 11.4 Signals and Flask’s Request Context..................... 68 11.5 Decorator Based Signal Subscriptions.................... 68 11.6 Core Signals................................... 68 12 Pluggable Views 71 12.1 Basic Principle................................. 71 12.2 Method Hints.................................. 72 12.3 Method Based Dispatching.......................... 73 12.4 Decorating Views................................ 73 12.5 Method Views for APIs............................ 74 13 The Application Context 77 13.1 Purpose of the Application Context..................... 77 13.2 Creating an Application Context....................... 78 13.3 Locality of the Context............................. 78 14 The Request Context 79 14.1 Diving into Context Locals.......................... 79 14.2 How the Context Works............................ 80 14.3 Callbacks and Errors.............................. 80 14.4 Teardown Callbacks.............................. 81 14.5 Notes On Proxies................................ 82 14.6 Context Preservation on Error........................ 82 15 Modular Applications with Blueprints 85 15.1 Why Blueprints?................................ 85 15.2 The Concept of Blueprints........................... 86 15.3 My First Blueprint............................... 86 15.4 Registering Blueprints............................. 86 15.5 Blueprint Resources.............................. 87 15.6 Building URLs................................. 88 16 Flask Extensions 91 16.1 Finding Extensions............................... 91 16.2 Using Extensions................................ 91 16.3 Flask Before 0.8................................. 91 17 Working with the Shell 93 17.1 Creating a Request Context.......................... 93 17.2 Firing Before/After Request......................... 94 17.3 Further Improving the Shell Experience................... 94 18 Patterns for Flask 95 18.1 Larger Applications.............................. 95 18.2 Application Factories............................. 97 18.3 Application Dispatching............................ 99 iii 18.4 Using URL Processors............................. 102 18.5 Deploying with Distribute.......................... 104 18.6 Deploying with Fabric............................. 107 18.7 Using SQLite 3 with Flask........................... 111 18.8 SQLAlchemy in Flask............................. 113 18.9 Uploading Files................................. 117 18.10 Caching..................................... 120 18.11 View Decorators................................ 121 18.12 Form Validation with WTForms....................... 124 18.13 Template Inheritance.............................. 127 18.14 Message Flashing................................ 128 18.15 AJAX with jQuery............................... 131 18.16 Custom Error Pages.............................. 134 18.17 Lazily Loading Views............................. 135 18.18 MongoKit in Flask............................... 137 18.19 Adding a favicon................................ 139 18.20 Streaming Contents.............................. 140 18.21 Deferred Request Callbacks.......................... 142 19 Deployment Options 145 19.1 mod_wsgi (Apache).............................. 145 19.2 Standalone WSGI Containers......................... 148 19.3 uWSGI...................................... 150 19.4 FastCGI..................................... 151 19.5 CGI........................................ 155 20 Becoming Big 157 20.1 Read the Source................................. 157 20.2 Hook. Extend.................................. 157 20.3 Subclass...................................... 157 20.4 Wrap with middleware............................. 158 20.5 Fork........................................ 158 20.6 Scale like a pro.................................. 158 20.7 Discuss with the community.......................... 159 II API Reference 161 21 API 163 21.1 Application Object............................... 163 21.2 Blueprint Objects................................ 182 21.3 Incoming Request Data............................ 186 21.4 Response Objects................................ 188 21.5 Sessions..................................... 189 21.6 Session Interface................................ 190 21.7 Test Client.................................... 192 21.8 Application Globals.............................. 193 21.9 Useful Functions and Classes......................... 193 21.10 Message Flashing................................ 200 iv 21.11 Returning JSON................................ 201 21.12 Template Rendering.............................. 202 21.13 Configuration.................................. 203 21.14 Extensions.................................... 204 21.15 Stream Helpers................................. 205 21.16 Useful Internals................................. 205 21.17 Signals...................................... 208 21.18 Class-Based Views............................... 209 21.19 URL Route Registrations........................... 210 21.20 View Function Options............................ 212 III Additional Notes 215 22 Design Decisions in Flask 217 22.1 The Explicit Application Object........................ 217 22.2 The Routing System.............................. 218 22.3 One Template Engine............................. 218 22.4 Micro with Dependencies........................... 219 22.5 Thread Locals.................................. 220 22.6 What Flask is, What Flask is Not....................... 220 23 HTML/XHTML FAQ 221 23.1 History of XHTML............................... 221 23.2 History of HTML5............................... 222 23.3 HTML versus XHTML............................
Recommended publications
  • Next Generation Web Scanning Presentation
    Next generation web scanning New Zealand: A case study First presented at KIWICON III 2009 By Andrew Horton aka urbanadventurer NZ Web Recon Goal: To scan all of New Zealand's web-space to see what's there. Requirements: – Targets – Scanning – Analysis Sounds easy, right? urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com Targets What does 'NZ web-space' mean? It could mean: •Geographically within NZ regardless of the TLD •The .nz TLD hosted anywhere •All of the above For this scan it means, IPs geographically within NZ urbanadventurer (Andrew Horton) www.morningstarsecurity.com Finding Targets We need creative methods to find targets urbanadventurer (Andrew Horton) www.morningstarsecurity.com DNS Zone Transfer urbanadventurer (Andrew Horton) www.morningstarsecurity.com Find IP addresses on IRC and by resolving lots of NZ websites 58.*.*.* 60.*.*.* 65.*.*.* 91.*.*.* 110.*.*.* 111.*.*.* 113.*.*.* 114.*.*.* 115.*.*.* 116.*.*.* 117.*.*.* 118.*.*.* 119.*.*.* 120.*.*.* 121.*.*.* 122.*.*.* 123.*.*.* 124.*.*.* 125.*.*.* 130.*.*.* 131.*.*.* 132.*.*.* 138.*.*.* 139.*.*.* 143.*.*.* 144.*.*.* 146.*.*.* 150.*.*.* 153.*.*.* 156.*.*.* 161.*.*.* 162.*.*.* 163.*.*.* 165.*.*.* 166.*.*.* 167.*.*.* 192.*.*.* 198.*.*.* 202.*.*.* 203.*.*.* 210.*.*.* 218.*.*.* 219.*.*.* 222.*.*.* 729,580,500 IPs. More than we want to try. urbanadventurer (Andrew Horton) www.morningstarsecurity.com IP address blocks in the IANA IPv4 Address Space Registry Prefix Designation Date Whois Status [1] -----
    [Show full text]
  • Flask Documentation Release 0.7Dev July 14, 2014
    Flask Documentation Release 0.7dev July 14, 2014 Contents I User’s Guide1 1 Foreword3 1.1 What does “micro” mean?...........................3 1.2 A Framework and an Example........................4 1.3 Web Development is Dangerous.......................4 1.4 The Status of Python 3.............................4 2 Installation7 2.1 virtualenv....................................7 2.2 System Wide Installation...........................8 2.3 Living on the Edge...............................9 2.4 easy_install on Windows............................9 3 Quickstart 11 3.1 A Minimal Application............................ 11 3.2 Debug Mode.................................. 12 3.3 Routing..................................... 13 3.4 Static Files.................................... 17 3.5 Rendering Templates.............................. 17 3.6 Accessing Request Data............................ 19 3.7 Redirects and Errors.............................. 22 3.8 Sessions..................................... 22 3.9 Message Flashing................................ 23 3.10 Logging..................................... 24 3.11 Hooking in WSGI Middlewares....................... 24 4 Tutorial 25 4.1 Introducing Flaskr............................... 25 4.2 Step 0: Creating The Folders......................... 26 4.3 Step 1: Database Schema........................... 27 4.4 Step 2: Application Setup Code........................ 27 i 4.5 Step 3: Creating The Database........................ 29 4.6 Step 4: Request Database Connections.................... 30 4.7 Step
    [Show full text]
  • Azure Increase Request Timeout
    Azure Increase Request Timeout Is Val snobby or uninaugurated after regimented Ulric inactivate so yet? Wakefield yo-ho indefeasibly as un-American Shadow bomb her Cherokee interwreathed unsystematically. Jeffrey metricize her peafowl unharmfully, avaricious and dozing. This can increase azure request timeout error and start work only Use this field to test small chunks of CSS code. If all else fails, there are many other settings that can be changed. The other consideration is this is per server so in multiple servers, it provides another means of segmenting load and configuring the resources differently for direct API requests and browser requests for HTML and CSS content. With the fast growing adoption of Kubernetes, and tutorials every week. Any configurable properties can have visited kinsta has django and request timeout for getting the signing region for sending various breaches where it can scale. Are you sure you want to allow comments on this post? Azure slot that webjobs are executed on the real website as well as the staging slot. Activity function to do the actual processing. If your browser shows an error message instead of the website you wanted to open, or arrange a chat, the operation was completely transparent and it has no idea such a transformation happened. This article is too good. Turn your data into revenue, missing, but nothing else. Http trigger azure website with his wife, application times out that clients can increase azure key. The first one was to serialize with a max depth. In the end, the reality slightly altered. As there exist a variety of operating systems, or the API platform.
    [Show full text]
  • Estudio De Web Servers
    UNIVERSIDADE DE VIGO ESCOLA SUPERIOR DE ENXEÑERÍA INFORMÁTICA Proyecto ACSO CURSO 2009/2010 Alumnos: Miguel Portela González Aarón Veiga Olivera Miguel Bermúdez Pena Noelia Pérez Álvarez 1.- INTRODUCCIÓN 2.- ESTADO DEL ARTE 3.- DESCRIPCIÓN TÉCNICA Y CONFIGURACIÓN • CHEROKEE • LIGHTTPD • APACHE • THTTPD 4.- RESULTADOS Y MEDICIONES EXPERIMENTALES 5.- INTERPRETACIÓN DE RESULTADOS 6.- CONCLUSIONES ESTUDIO DE LOS SERVIDORES CHEROKEE APACHE LIGHTTPD THTTPD PROPÓSITO DEL ESTUDIO MEDIR PARÁMETROS DE LOS SERVIDORES COMPROBAR CUÁL DE LOS SERVIDORES ES MEJOR REALIZAR GRÁFICAS DE LOS RESULTADOS OBTENER RESULTADOS Y CONCLUSIONES RESULTADOS ESPERADOS Será un articulo que ayude a una persona que necesite montar un servidor en su empresa para seleccionar la mejor opción. Los motivos y razones estarán fundamentadas en las pruebas y mediciones realizadas No hay estudios similares en la Web Ventajas y desventajas del software y herramientas utilizados DESVENTAJAS VENTAJAS Versiones de los servidores Servidor Versión Cherokee 0.99.19 Lighttpd 1.04.22 Apache 2.02.12 Thttpd 2.25b-6 Plataforma de pruebas CPU Intel Core Duo T2400 1.83GHz HDD Western Digital 250 GB 2.5 5400 rpm ATA Video Ati Radeon X1600 PRO 256MB Memoria RAM 3GB Tarjeta Wireless Intel 3950 ABG S.O. Ubuntu 9.10 Karmic Kernel 2.6.32 Servidor web de alto rendimiento. Es muy rápido, flexible y fácil de configurar. Interfaz gráfica Software libre. Totalmente modular. Multiplataforma (rendimiento nativo para Unix, Linux y Windows). Es un servidor web diseñado para ser rápido, seguro, flexible, y fiel a los estándares. Está optimizado para entornos donde la velocidad es muy importante Es software libre La configuración se realiza mediante la edición de un archivo de texto Características: Virtual hosting CGI, SCGI y FastCGI Soporte para PHP, Ruby, Python y otros Cifrado SSL Compresión (gzip, bzip2, ...) Autenticación (LDAP, htpasswd, otros) … Servidor web flexible, rápido y eficiente, continuamente actualizado y adaptado a los nuevos protocolos.
    [Show full text]
  • 2009 Shareholders Report
    Volume 9, Issue 1 March 2010 Shareholders’ Report 2009 National Weather Service • Weather Forecast Office • Peachtree City, Georgia Status Quo is Not an Option! Lans P. Rothfusz bulk of the rain fell at a less- Meteorologist in Charge than-ideal time (in the middle of the night, at the end of a Big News Items of 2009 ike any Weather Fore- weekend). Forecasting such a cast Office (WFO) in the small-scale, rare and epic event • Historic Flooding (pages 6 and National Weather Ser- with reasonable lead time is un- 10) L vice (NWS) after a ma- fortunately beyond the state of • WFO Wins DOC Silver Medal jor weather event, the Peach- today’s science. Even if it were (page 3) tree City WFO looks carefully for possible, the public must still ways in which warning services respond appropriately. 24-hour rainfall ending September 21st • Decision Support Program and public response might be showing >16” bulls-eye (yellow) over Evolves (page 10) Douglas County. Warnings were in effect, improved. This was the case As you will see in this yet eight people perished in this area. after the deadly September newsletter, ours is not an office floods in North Georgia— that sits still. We pride reduce the loss of life and In Fiscal Year 2009, especially the fateful morning of ourselves in learning from every September 21 when flooding property over time, but they do Congress appropriated event we work. We will con- take time to develop. claimed the lives of ten people. tinue improving our science and $958,900,000 to the NWS To say this was an epic event is skills.
    [Show full text]
  • Python - a Crash Course
    Python - A Crash Course Antonio Lima Networks and Distributed Systems 2012-2013 School of Computer Science - University of Birmingham 15 March 2013 Last week's Homework Write a Python program that counts the occurrences of words in a wordlist. counter = {} with open(filename, "r") as f: for line in f: if line in counter: counter[line] += 1 else: counter[line] = 1 We are asking permission. It's easier to ask forgiveness. Last week's Homework You ask forgiveness by executing a task and recovering if there is an error. counter = {} with open(filename, "r") as f: for line in f: try: counter[line] += 1 except KeyError: counter[line] = 1 That's much better (one operation less). But there's even a more pythonic solution. Last week's Homework You ask forgiveness by executing a task and recovering if there is an error. import collections counter = collections.defaultdict(int) with open(filename, "r") as f: for line in f: counter[line] += 1 5 lines, very readable, correct. Pythonic. Why using Python for Networking? • Well, why not? • Many successful companies/startups are using it. • Google, Yahoo, Dropbox, Quora, Disqus, ... • A lot of libraries are available. • You can build prototypes quickly. The socket module: not only sockets The module provides access to the BSD socket interface. Very low-level. >>> import socket >>> hostname = 'google.com' >>> addr = socket.gothostbyname(hostname) '173.194.41.102' >>> socket.getservbyname('ssh') 22 >>> socket.getservbyname('http') 80 The socket module: a client-server application # Client import socket import
    [Show full text]
  • Comparison of Web Server Software from Wikipedia, the Free Encyclopedia
    Create account Log in Article Talk Read Edit ViewM ohrisetory Search Comparison of web server software From Wikipedia, the free encyclopedia Main page This article is a comparison of web server software. Contents Featured content Contents [hide] Current events 1 Overview Random article 2 Features Donate to Wikipedia 3 Operating system support Wikimedia Shop 4 See also Interaction 5 References Help 6 External links About Wikipedia Community portal Recent changes Overview [edit] Contact page Tools Server Developed by Software license Last stable version Latest release date What links here AOLserver NaviSoft Mozilla 4.5.2 2012-09-19 Related changes Apache HTTP Server Apache Software Foundation Apache 2.4.10 2014-07-21 Upload file Special pages Apache Tomcat Apache Software Foundation Apache 7.0.53 2014-03-30 Permanent link Boa Paul Phillips GPL 0.94.13 2002-07-30 Page information Caudium The Caudium Group GPL 1.4.18 2012-02-24 Wikidata item Cite this page Cherokee HTTP Server Álvaro López Ortega GPL 1.2.103 2013-04-21 Hiawatha HTTP Server Hugo Leisink GPLv2 9.6 2014-06-01 Print/export Create a book HFS Rejetto GPL 2.2f 2009-02-17 Download as PDF IBM HTTP Server IBM Non-free proprietary 8.5.5 2013-06-14 Printable version Internet Information Services Microsoft Non-free proprietary 8.5 2013-09-09 Languages Jetty Eclipse Foundation Apache 9.1.4 2014-04-01 Čeština Jexus Bing Liu Non-free proprietary 5.5.2 2014-04-27 Galego Nederlands lighttpd Jan Kneschke (Incremental) BSD variant 1.4.35 2014-03-12 Português LiteSpeed Web Server LiteSpeed Technologies Non-free proprietary 4.2.3 2013-05-22 Русский Mongoose Cesanta Software GPLv2 / commercial 5.5 2014-10-28 中文 Edit links Monkey HTTP Server Monkey Software LGPLv2 1.5.1 2014-06-10 NaviServer Various Mozilla 1.1 4.99.6 2014-06-29 NCSA HTTPd Robert McCool Non-free proprietary 1.5.2a 1996 Nginx NGINX, Inc.
    [Show full text]
  • Master Thesis
    MASTER THESIS TITLE: Analysis and evaluation of high performance web servers MASTER DEGREE: Master in Science in Telecommunication Engineering & Management AUTHOR: Albert Hidalgo Barea DIRECTOR: Rubén González Blanco SUPERVISOR: Roc Meseguer Pallarès DATE: July 13 th 2011 Title: Analysis and evaluation of high performance web servers Author: Albert Hidalgo Barea Director: Rubén González Blanco Supervisor: Roc Meseguer Pallarès Date: July 13 th 2011 Overview Web servers are a very important tool when providing users with requested content on the Internet. Usage of the Internet is growing day-by-day, making those software applications essential. In the first part of the thesis, the web server world will be introduced to the reader, by giving a brief explanation of some of the available technologies as well as different dynamic protocols. Also, as there are different web servers available in the market, during this report it will be chosen the best performing ones. So, it will be presented a comparative chart between all of them in order to show the most important features of each one. Defining the scenario and the test cases is mandatory. For this reason, it is described the used hardware and software used to perform those benchmarks. The hardware is maintained equal during the whole test process, in order to let web server’s performance gaps to their internal architecture. Operating system and benchmarking tools are also described and given some examples. Furthermore, test cases are chosen to show some strengths and weakness of each web server, enabling us to compare the relative performance between them. Finally, the last part of the report consists on presenting the obtained results during the benchmark process, as well as presenting some lessons learned during the curse of the whole thesis, summing-up with some conclusions.
    [Show full text]
  • Security Testing Tutorial
    Security Testing About the Tutorial Security Testing is performed to reveal security flaws in the system in order to protect data and maintain functionality. This tutorial explains the core concepts of Security Testing and related topics with simple and useful examples. Audience This tutorial has been prepared for beginners to help them understand the basics of security testing. Prerequisites Before proceeding with this tutorial, you should have a basic understanding of software testing and its related concepts. Copyright & Disclaimer ¬ Copyright 2017 by Tutorials Point (I) Pvt. Ltd. All the content and graphics published in this e-book are the property of Tutorials Point (I) Pvt. Ltd. The user of this e-book is prohibited to reuse, retain, copy, distribute or republish any contents or a part of contents of this e-book in any manner without written consent of the publisher. We strive to update the contents of our website and tutorials as timely and as precisely as possible, however, the contents may contain inaccuracies or errors. Tutorials Point (I) Pvt. Ltd. provides no guarantee regarding the accuracy, timeliness or completeness of our website or its contents including this tutorial. If you discover any errors on our website or in this tutorial, please notify us at [email protected] i Security Testing Table of Contents About the Tutorial ....................................................................................................................................... i Audience ....................................................................................................................................................
    [Show full text]
  • An Introduction to Python for Absolute Beginners
    An introduction to Python for absolute beginners Bob Dowling University Computing Service [email protected] http://www.ucs.cam.ac.uk/docs/course-notes/unix-courses/PythonAB 1 Welcome to the Computing Service's course “Introduction to Python”. This course is designed for people with absolutely no experience of programming. If you have any experience in programming other languages you are going to find this course extremely boring and you would be better off attending our course "Python for Programmers" where we teach you how to convert what you know from other programming languages to Python. This course is based around Python version 3. Python has recently undergone a change from Python 2 to Python 3 and there are some incompatibilities between the two versions. The older versions of this course were based around Python 2 but this course is built on Python 3. Python is named after Monty Python and its famous flying circus, not the snake. It is a trademark of the Python Software Foundation. 1 Course outline ― 1 Who uses Python & what for What sort of language it is How to launch Python Python scripts Text Names for values Reading in user data Numbers Conversions Comparisons Truth & Falsehood 2 2 Course outline ― 2 Assignment Names Our first “real” program Loops if… else… Indentation Comments 3 3 Course outline ― 3 Lists Indices Lengths Changing items Extending lists Methods Creating lists Testing lists Removing from lists for… loop Iterables Slices 4 4 Course outline ― 4 Files Reading & writing Writing our own functions
    [Show full text]
  • Computer System Administration. Topic 9. Secure Web Service: HTTP
    Computer System Design and Administration Topic 9. Secure web service: HTTP Apache2 (over SSL) José Ángel Herrero Velasco Department of Computer and Electrical Engineering This work is published under a License: Creative Commons BY-NC-SA 4.0 Computer System Design and Administration Topic 9. Secure web service: HTTP Apache2 (over SSL) WEB service (HTTP): Puzzle Secure information server SSH Active ISC Clients Directory DHCP Open ISC SSL SSL LDAP DB LDAP client DNS OpenLDAP ISC SSL NTP server:/ //server/ export export Secure WEB server NFSv4 CIFS PHP MySQL LDAP User (web data) pool Apache2 (public_html) Network file server/ MS Windows-Linux/UNIX interoperability SSL SSL RAID/LVM /dev/ Core (web data) pool /dev/ sdxx SAMBA NFSv4 (.html, php…) Hosts Virtual /dev/ sdxx CMS: WordPress sdxx José Ángel Herrero Velasco Computer System Design and Administration Topic 9. Secure web service: HTTP Apache2 (over SSL) Target: WEB services • Deployment and development of an INTERNET secure WEB service based on Apache server: – Content management. – Access control. – Virtualhost concept (management). – Secure communicaons: TLS/SSL. • Installaon, configuraon and start-up of a Web Content Manager (CMS): – Wordpress. José Ángel Herrero Velasco Computer System Design and Administration Topic 9. Secure web service: HTTP Apache2 (over SSL) HTTP: The protocol • The HTTP (Hypertext Transfer Protocol) protocol: – Definion: • The Hypertext Transfer Protocol (HTTP) is an applicaon-level protocol for distributed, collaboraBve, hypermedia informaon systems: – Enables exchanging informaon (text, mulmedia...). – Most common method of informaon exchange on WWW - Since 1990. – Syntax and semanBcs. – THe informaon excHanged: • The HyperText Markup Language (HTML): – Hypertext is structured text that uses logical links between nodes with contents TCP/IP Stack (plain text): » Message excHange methods: • HEAD,GET,POST… – Used by soware elements on the WEB architecture: » Clients (browsers), servers and proxies.
    [Show full text]
  • Software Engineer - Lighthouse Team
    Software Engineer - Lighthouse team SUMMARY Opengear designs and manufactures products for sophisticated data center and remote site management. We are looking for Software Engineers (minimum 2 years' experience) to join our development team in Brisbane, Australia. The engineering team develops and maintains the software for Opengear console servers and management appliances. Our devices run embedded linux, with a mix of open-source tools (eg. OpenSSH, OpenVPN, NUT, Cherokee, nginx, etc.) and our own proprietary additions (serial management, CGI web interface, HTTP and REST APIs, monitoring daemons, etc.). We work in a wide and varied code base, covering many fields -- embedded development, kernel development, networking, security, serial interfaces, web interfaces, web development, and so on. This role is centered around work on our management appliance, which ships on an server, or as a virtual machine. It is used for centralising access and monitoring for large estates of Opengear hardware appliances. ESSENTIAL DUTIES AND RESPONSIBILITIES You will be working on the software for our embedded Linux console servers and management appliance. Your duties will include: • Feature development from initial scoping and design to deployment and long term maintenance. • Providing assistance for escalated customer issues (diagnosing and fixing bug reports). • Developer level testing, and assisting the test team with generating test plans. • General infrastructure maintenance as required (build system, source control system, etc.). QUALIFICATIONS Our engineers are expected to be able to work on any part of the software stack, from the operating system up to the Web front end. You will be working in a variety of languages, including C and C++, Lua, Bash, and Javascript.
    [Show full text]