List developed by the attendees at WordCamp Philly 2014 Contributor Day
Steps to Reproduce
- List of steps
Enviornment
- Browser Version
- PHP Version
- MySql Version
- WordPress Version
httpClient.DefaultRequestHeaders.Authorization = | |
new AuthenticationHeaderValue( | |
"Basic", | |
Convert.ToBase64String( | |
System.Text.ASCIIEncoding.ASCII.GetBytes( | |
string.Format("{0}:{1}", username, password)))); |
List developed by the attendees at WordCamp Philly 2014 Contributor Day
Steps to Reproduce
Enviornment
jQuery( function () { | |
My_Object.init(); | |
} ); | |
(function ( $, app ) { | |
/** | |
* Bootstrap | |
*/ | |
app.init = function() { |
<?php | |
/** | |
* | |
* There are use cases where using filter_var( FILTER_SANITIZE_STRING ) is not desireable because it is too greedy. | |
* In the event that you have written a more permissive xss cleaning routine this unit test can be used to test your | |
* cleaning routine. The list of attack vectors is not comprehensive but should give you a good start. | |
* | |
* The detection routine below is based on https://github.com/symphonycms/xssfilter/blob/master/extension.driver.php | |
* and on https://gist.github.com/mbijon/1098477 |
/** | |
* | |
* Force http/s for images in WordPress | |
* | |
* Source: | |
* https://core.trac.wordpress.org/ticket/15928#comment:63 | |
* | |
* @param $url | |
* @param $post_id | |
* |
{ | |
"name": "my-app", | |
"version": "1.0.0", | |
"description": "My test app", | |
"main": "src/js/index.js", | |
"scripts": { | |
"jshint:dist": "jshint src/js/*.js", | |
"jshint": "npm run jshint:dist", | |
"jscs": "jscs src/*.js", | |
"browserify": "browserify -s Validating -o ./dist/js/build.js ./lib/index.js", |
# the IP(s) on which your node server is running. I chose port 3000. | |
upstream app_geoforce { | |
server 127.0.0.1:3000; | |
} | |
upstream app_pcodes{ | |
server 127.0.0.1:3001; | |
} |
adapter: s3 | |
bucket_name: queen-fantasia | |
access_key_id: my_key_id | |
secret_access_key: my_secret_access_key | |
host: s3-sa-east-1.amazonaws.com | |
exclude: | |
- .gitignore | |
- dandelion.yml |
The standard way of understanding the HTTP protocol is via the request reply pattern. Each HTTP transaction consists of a finitely bounded HTTP request and a finitely bounded HTTP response.
However it's also possible for both parts of an HTTP 1.1 transaction to stream their possibly infinitely bounded data. The advantages is that the sender can send data that is beyond the sender's memory limit, and the receiver can act on