| <?php | |
| function tinker(...$args) { | |
| // Because there is no way of knowing what variable names | |
| // the caller of this function used with the php run-time, | |
| // we have to get clever. My solution is to peek at the | |
| // stack trace, open up the file that called "tinker()" | |
| // and parse out any variable names, so I can load | |
| // them in the tinker shell and preserve their names. |
| ## | |
| ## How to install mcrypt in php7.2 / php7.3 | |
| ## Linux / MacOS / OSX | |
| ## | |
| ## https://lukasmestan.com/install-mcrypt-extension-in-php7-2/ | |
| # |
Source: http://www.syahzul.com/2016/04/06/how-to-install-oci8-on-ubuntu-14-04-and-php-5-6/
Download the Oracle Instant Client and SDK from Oracle website. (Need to login in Oracle page)
http://www.oracle.com/technetwork/topics/linuxx86-64soft-092277.html
Nice answer on stackoverflow to the question of when to use one or the other content-types for POSTing data, viz. application/x-www-form-urlencoded and multipart/form-data.
“The moral of the story is, if you have binary (non-alphanumeric) data (or a significantly sized payload) to transmit, use multipart/form-data. Otherwise, use application/x-www-form-urlencoded.”
Matt Bridges' answer in full:
The MIME types you mention are the two Content-Type headers for HTTP POST requests that user-agents (browsers) must support. The purpose of both of those types of requests is to send a list of name/value pairs to the server. Depending on the type and amount of data being transmitted, one of the methods will be more efficient than the other. To understand why, you have to look at what each is doing
| """ | |
| Pseudo-random django secret key generator. | |
| - Does print SECRET key to terminal which can be seen as unsafe. | |
| """ | |
| import string | |
| import random | |
| from __future__ import print_function |
