On 23.12.2021 at 16:53, Hans Henrik Bergan wrote:
> another thing, it wouldn't surprise me if someone at some point want to
> emulate some IIS-specific codes in PHP, like
> header("HTTP/1.1 401.3 Unauthorized due to ACL on resource.");
>
> it'd be a shame if PHP literally cannot send IIS-errorcode
another thing, it wouldn't surprise me if someone at some point want to
emulate some IIS-specific codes in PHP, like
header("HTTP/1.1 401.3 Unauthorized due to ACL on resource.");
it'd be a shame if PHP literally cannot send IIS-errorcodes
On Thu, 23 Dec 2021 at 16:40, Hans Henrik Bergan
wrote:
sometime in the future HTTP 6xx will be defined, and we'll have to add a
big warning to the header()/http_respons_code() pages like
"Warning: HTTP 6.x.x is only supported in PHP >= x.x.x and PHP <=8.1.x",
and library developers have to add fugly code like
`if(PHP_VERSION_MAJOR >= X || (PHP_VERSION_
On Thu, 23 Dec 2021, 00:06 David Gebler, wrote:
> On Tue, Dec 21, 2021 at 6:59 PM Christoph M. Becker
> wrote:
>
> > Hi all,
> >
> > a while ago it has been reported[1] that our header() function actually
> > allows arbitrary status codes, which may even overflow. Of course, that
> > makes no s
On Tue, Dec 21, 2021 at 6:59 PM Christoph M. Becker
wrote:
> Hi all,
>
> a while ago it has been reported[1] that our header() function actually
> allows arbitrary status codes, which may even overflow. Of course, that
> makes no sense, since the status code is supposed to be a three digit
> cod
On 21.12.2021 at 20:09, Ayesh Karunaratne wrote:
>> a while ago it has been reported[1] that our header() function actually
>> allows arbitrary status codes, which may even overflow. Of course, that
>> makes no sense, since the status code is supposed to be a three digit
>> code. So this ticket
>
> Hi all,
>
> a while ago it has been reported[1] that our header() function actually
> allows arbitrary status codes, which may even overflow. Of course, that
> makes no sense, since the status code is supposed to be a three digit
> code. So this ticket has been followed up by a pull request[2
Hi all,
a while ago it has been reported[1] that our header() function actually
allows arbitrary status codes, which may even overflow. Of course, that
makes no sense, since the status code is supposed to be a three digit
code. So this ticket has been followed up by a pull request[2], and
Jakub
