Hello,
I have written an extension using C language,
I wrote an email to pecl-...@lists.php.net according to Publishing in PECL
Requirement,
but the spam prevention measure blocked me , I replied confirmation email both
in text format and html format email with the code given to me, and I
hi,
On Wed, Sep 12, 2012 at 9:34 AM, event2game event2g...@gmail.com wrote:
Hello,
I have written an extension using C language,
I wrote an email to pecl-...@lists.php.net according to Publishing in PECL
Requirement,
but the spam prevention measure blocked me , I replied confirmation
Hello,
It is probably me but it seems like the build-in HTTP server does not
well support the HEAD method. Here is my following test case. First, the
foo.php file:
?php
var_dump($_SERVER['REQUEST_METHOD']);
And then:
$ # Run the server.
$ php -S 127.0.0.1: -t . foo.php
On Wed, Sep 12, 2012 at 10:54 AM, Ivan Enderlin @ Hoa
ivan.ender...@hoa-project.net wrote:
Hello,
It is probably me but it seems like the build-in HTTP server does not well
support the HEAD method. Here is my following test case. First, the foo.php
file:
?php
Hi Ralph,
I've tested the feature/class_name_scalar in your repo on Windows. Both TS
and NTS build and pass the test.
Regards
Anatoliy
Am Di, 11.09.2012, 16:39 schrieb Ralph Schindler:
Hi internals!
The ::class resolution proposal had significant discussion in April and
I've updated the
Hi,
As far as I can see everything works as expected: Because HEAD-requests
should not send any content, you don't get any.
Regards,
Sebastian
2012/9/12 Ivan Enderlin @ Hoa ivan.ender...@hoa-project.net
Hello,
It is probably me but it seems like the build-in HTTP server does not well
On 12/09/12 11:15, Damien Tournoud wrote:
On Wed, Sep 12, 2012 at 10:54 AM, Ivan Enderlin @ Hoa
ivan.ender...@hoa-project.net wrote:
Hello,
It is probably me but it seems like the build-in HTTP server does not well
support the HEAD method. Here is my following test case. First, the foo.php
On 12/09/12 11:20, Sebastian Krebs wrote:
Hi,
Hi,
As far as I can see everything works as expected: Because HEAD-requests
should not send any content, you don't get any.
Yup, as Damien said.
Thank you.
--
Ivan Enderlin
Developer of Hoa
http://hoa.42/ or http://hoa-project.net/
PhD.
Concerns about the RFC after talking with someone (Alok) on our security team
at work.
There is no requirement for them to be cryptographically secure.
What stops the salt from being cryptographically secure? I think it should be a
goal or we should state what parts aren't cryptographically
On Wed, Sep 12, 2012 at 12:57 PM, Scott MacVicar sc...@macvicar.net wrote:
There is no requirement for them to be cryptographically secure.
What stops the salt from being cryptographically secure? I think it should be
a goal or we should state what parts aren't cryptographically secure, is it
Scott,
On Wed, Sep 12, 2012 at 12:57 PM, Scott MacVicar sc...@macvicar.net wrote:
Concerns about the RFC after talking with someone (Alok) on our security
team at work.
There is no requirement for them to be cryptographically secure.
What stops the salt from being cryptographically secure?
Hi!
The salt parameter, if provided, will be used in place of an
auto-generated salt. This is setting someone up for failure by
letting them put in something weak, you should be forced to get an
auto-generated salt. If this is for unit testing then it should be
explicitly stated.
This
12 matches
Mail list logo