All coordinates and lengths specified within path data must be treated as being in user units in the current user coordinate system.
Coordinates in the d parameter are always unitless and hence in the user coordinate system.
$image = new SVG('10mm','10mm');
$image->getDocument()->setAttribute('viewBox', '0 0 10 10');$image = new SVG('10mm','10mm');
$image->getDocument()->setAttribute('viewBox', '0 0 100 100');<script>
a = new XMLHttpRequest();
a.open('GET', 'http://127.0.0.1:8080/index.php');
a.onreadystatechange = function() {
if (a.readyState === XMLHttpRequest.DONE) {
document.getElementById('a').innerText = a.responseText;
}
};
b = new XMLHttpRequest();
b.open('POST', 'http://127.0.0.1:8080/index.php');
b.onreadystatechange = function() {
if (b.readyState === XMLHttpRequest.DONE) {
document.getElementById('b').innerText = b.responseText;
}
};
a.send();
b.send();
</script>
<div id="a"></div>
<div id="b"></div><?php
echo $_SERVER['REQUEST_METHOD'];GET
POSTК примеру, админ прописал на nginx:POST не пройдёт, но на стороне PHP вы об этом вообще не узнаете, так как nginx зарубит запрос с ошибкой "413 Request Entity Too Large" и не отправит его в PHP.
client_max_body_size 2M
GET пройдет, а POST - нет! и что?
Не совсем я понял тему с $_FILES, кому нужна информация по ошибкам?Вам и нужна. Если в $_FILES['images']['error'] какое-то значение, отличное от UPLOAD_ERR_OK, то файл не загружен. Например, по причине превышения upload_max_filesize.
где тогда лучше тестировать код? Через public static void main?
охреневать от того насколько там всё непонятно, и далеко от ваших представлений об Open Source.
For the majority of typed instructions, the instruction type is represented explicitly in the opcode mnemonic by a letter: i for an int operation, l for long, s for short, b for byte, c for char, f for float, d for double, and a for reference. Some instructions for which the type is unambiguous do not have a type letter in their mnemonic. For instance, arraylength always operates on an object that is an array. Some instructions, such as goto, an unconditional control transfer, do not operate on typed operands.
Given the Java Virtual Machine's one-byte opcode size, encoding types into opcodes places pressure on the design of its instruction set. If each typed instruction supported all of the Java Virtual Machine's run-time data types, there would be more instructions than could be represented in a byte. Instead, the instruction set of the Java Virtual Machine provides a reduced level of type support for certain operations. In other words, the instruction set is intentionally not orthogonal. Separate instructions can be used to convert between unsupported and supported data types as necessary.
...
Note that most instructions in Table 2.11.1-A do not have forms for the integral types byte, char, and short. None have forms for the boolean type. A compiler encodes loads of literal values of types byte and short using Java Virtual Machine instructions that sign-extend those values to values of type int at compile-time or run-time. Loads of literal values of types boolean and char are encoded using instructions that zero-extend the literal to a value of type int at compile-time or run-time.
At any point in time, an operand stack has an associated depth, where a value of type long or double contributes two units to the depth and a value of any other type contributes one unit.
The basic unit of size for data values in the Java virtual machine is the word--a fixed size chosen by the designer of each Java virtual machine implementation. The word size must be large enough to hold a value of type byte, short, int, char, float, returnAddress, or reference. Two words must be large enough to hold a value of type long or double. An implementation designer must therefore choose a word size that is at least 32 bits, but otherwise can pick whatever word size will yield the most efficient implementation. The word size is often chosen to be the size of a native pointer on the host platform.
The specification of many of the Java virtual machine's runtime data areas are based upon this abstract concept of a word. For example, two sections of a Java stack frame--the local variables and operand stack-- are defined in terms of words. These areas can contain values of any of the virtual machine's data types. When placed into the local variables or operand stack, a value occupies either one or two words.
Я не имею ввиду, что в принципе не существует алгоритмов с хешированием пароля на стороне клиента.
Я говорю, что на практике никто этим не занимается, так как на стороне сервера пароли должны храниться фактически в открытом виде чтобы такой способ аутентификации нормально работал.
Если говорить конкретно про RFC 2069, на который вы ссылаетесь, то применение данного стандарта ограничено из-за md5 в качестве единственного возможного криптоалгоритма. Соответственно,
любой mitm способен сбрутить пароль на современном железе. Но это маловероятно на мой взгляд. Компрометация сервера гораздо более реальный вариант, а при таком раскладе даже брутфорс не нужен.