Increasingly technologies that power the web platform require HTTPS to function (HTTP/2, Service Workers etc.), but there is still a surprising amount of friction involved in trying to setup a local HTTPS enabled development environment.
In this post, our goal is to configure a Mac to provide HTTPS with a trusted certificate using nginx as the web server.
We have the following goals:
https://example.sites.localdomain will be served by: ~/sites/example.sites.localdomain/index.html The above URL will have a fully trusted certificate with a padlock in Chrome/Safari.
Read more...
Shiny New Things For what seems like the longest time I’ve been an avid embracer of anything new in the tech sphere, especially so on the Web. I think I created my first home page back in early 1995 (unfortunately it vanished before The Web Archive could crawl it), and around the same time I had a GeoCities page, also lost to history. Then followed Hotmail, GMail, Flickr, YouTube, Facebook, LinkedIn, Twitter, Google+, about.
Read more...
Introduction Oracle REST Data Services (ORDS) provides an easy to use mechanism to transform relational result sets into JSON representations, and can even automatically paginate the result set, providing hyperlinks to navigate amongst the pages of the result set.
For many use cases it would be convenient to able to treat certain columns in the result set as hyperlinks, and ORDS supports a couple of mechanisms to do this:
Primary Key Hyperlinks - A column given the reserved alias $.
Read more...
Introduction Oracle REST Data Services (ORDS) understands two kinds of named parameter binds that can be used in the source of a resource handler statement:
Explicit - Explicit parameters are defined by the Resource Handler author using the ords.define_parameter API procedure. They can be used to map request headers to bind parameters and also used to bind outbound values to response headers. Implicit - Implicit parameters are defined by ORDS, they’re automically available to use, rather than needing to be explicitly declared.
Read more...
Introduction Oracle REST Data Services (ORDS) has a number of implicit parameters which may be bound into Resource Module Handlers. One of which is :current_user which provides the identity of the user authenticated for the current request. If a user has not been authenticated then value of :current_user will be null.
Example We can bind the value of :current_user into the context of a query as shown below:
begin ords.define_service( p_module_name => 'current.
Read more...