Hi!
> It's possible to design web pages/services to "unknown clients", but
> it's exceptional cases.
No, it's not. Every service exposed to the internet is for unknown clients.
> Almost all systems have intended clients. If protocol is HTTP/HTTPS,
> developers may reject strange data that cannot
On Fri, Aug 19, 2016 at 11:52 AM, Stanislav Malyshev
wrote:
> Hi!
>
>> I explicitly asked Aaron to wait for me to check out things today.
>> Indeed, it is a mess, but it would probably already have been reverted
>> if we managed to verify the issues earlier on. :-)
>
> OK, please tell when you're
On 2016-08-19 21:41, Nikita Popov wrote:
Instead, let's first introduce an object-based PRNG interface, which
a) does not rely on volatile global state and b) is explicit about the
choice of algorithm and seeding procedure.
That would be a nice solution. However, that's a task for someone
who a
On 20.08.2016 at 10:31, Rodrigue Villetard wrote:
> What we would like, is more:
> * Explicit remaining time to live of a deprecated feature (ie. in
> which future version of php this deprecated functionality will be
> dropped)
> * More ergonomics and normalized deprecations messages
+1
--
On 20/08/16 08:30, Yasuo Ohgaki wrote:
> The input validation we are discussing is "Input/output rules between
> client and server". It decides what's valid/invalid.
I think I'm getting two things confused and am mixing your array
filtering RFC up with this one. There is so much speculative stuff
Hi Pierre,
On Sat, Aug 20, 2016 at 4:57 PM, Pierre Joye wrote:
>> I'm planning to propose "Filter module deprecation" when this RFC
>> is declined, because current validation filter is not good enough to
>> do the job and makes situation worse than better... If deprecation
>> RFC is declined also
On 20 August 2016 at 07:56, Pierre Joye wrote:
>
> Hi,
>
> On Aug 19, 2016 8:45 PM, "Rodrigue Villetard"
> wrote:
> >
> > Hello everyone,
> >
> > First post here, so please be gentle and pedagogic with me if I am
> > misbehaviouring…
> >
> > I am here for a pre-RFC feedback. It’s not coding rela
On Aug 17, 2016 12:20 PM, "Yasuo Ohgaki" wrote:
>
> Hi Dan,
>
> I understood about RFC process.
>
> On Wed, Aug 17, 2016 at 12:23 PM, Dan Ackroyd
wrote:
> > Additionally, you seem to completely have ignored this:
> >
> > Dan Ackroyd wrote:
> >> And I strongly object to the idea of stopping and st
Hi Lester,
On Thu, Aug 18, 2016 at 4:27 PM, Lester Caine wrote:
> On 18/08/16 07:54, Stanislav Malyshev wrote:
>>> Broken char encoding shouldn't came from legitimate users. Text
>>> > contains CNTRL chars from shouldn't
>>> > come from legitimate users. 1MB data from >> > name="var" /> shouldn'
Hi Stas,
On Thu, Aug 18, 2016 at 3:54 PM, Stanislav Malyshev wrote:
>> Even when there is no JavaScript nor HTML5 forms, input validations
>> can be done. It's matter of definition of "valid inputs" for > type="text" name="var" />. If page encoding is UTF-8, web browsers
>> must return response b
10 matches
Mail list logo
