Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:115763 Return-Path: Delivered-To: mailing list internals@lists.php.net Received: (qmail 38507 invoked from network); 18 Aug 2021 12:55:37 -0000 Received: from unknown (HELO php-smtp4.php.net) (45.112.84.5) by pb1.pair.com with SMTP; 18 Aug 2021 12:55:37 -0000 Received: from php-smtp4.php.net (localhost [127.0.0.1]) by php-smtp4.php.net (Postfix) with ESMTP id A93521804CF for ; Wed, 18 Aug 2021 06:28:03 -0700 (PDT) X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on php-smtp4.php.net X-Spam-Level: * X-Spam-Status: No, score=1.8 required=5.0 tests=BAYES_20,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,FREEMAIL_ENVFROM_END_DIGIT, FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H2, SPF_HELO_NONE,SPF_PASS,URIBL_SBL,URIBL_SBL_A autolearn=no autolearn_force=no version=3.4.2 X-Spam-ASN: AS15169 209.85.128.0/17 X-Spam-Virus: No X-Envelope-From: Received: from mail-qk1-f173.google.com (mail-qk1-f173.google.com [209.85.222.173]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange ECDHE (P-256) server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by php-smtp4.php.net (Postfix) with ESMTPS for ; Wed, 18 Aug 2021 06:28:03 -0700 (PDT) Received: by mail-qk1-f173.google.com with SMTP id y144so2937187qkb.6 for ; Wed, 18 Aug 2021 06:28:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=xZG+9Pw62DKsvwKH80b1G1CXlihfKYxHrGB4OcBU7lY=; b=LLlLVWKcrwG4Lr3z6rnyP5R5Qc17h22e4tXPW7HFH9ZVHDHwVh1Mq3Ko8ZWYEcI1IK X0H6PBxrFAifPF+k+mUnDpV1511qdEs01LKPxfDelJ3nKYFOV9bVz85s4lNp/1s9eFh0 BnAnIVpEANihHGQaCvOibpyUp75pyaCCyXFGt5pr6hNKkJVWAbRYLkn6mrP+D2fWz9AP GZTT81xgYHm5FBRl8m2+OWT2hAGeh0POEpaqkhk5Wob6ae6bEpGFxzmm3q+N5miZvtk0 YxQIX0BTlj8n4onUwtHK6QMpm3DPsqkWjJS4dCHdHcxrFM22bmvW/+iEsAu0bb18wblh Gekg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=xZG+9Pw62DKsvwKH80b1G1CXlihfKYxHrGB4OcBU7lY=; b=U0PyL9Tpuj8mSxdbtlpbhw3AoH/XCbIE9thvMwXcoX6R/TWqJF5elPXs6tEmxYW+zo ak9kq5FunN3LyUCvFJdzk58K/9p9lp6vNoUQFKxz4wxiCbNjdawt554sjOCBWFKtqQod S1ckEym6JUtpcZDT9krUGxgpoVZYk/rGwWssqONhPzLvJjxCs5wKVxk7ymDra+1TCIZw iXEFM6gCNnZvQ98Bk8gawd4iPP58lEXpSDSySoBtzdUNDZRsKNE4m2uXRs69qpkVfyKx 3OcSPYgP0UnRAwkc8NWNNMTruVT9p3kinp2IgkqofDchmcBmQKmkEXAKVbA8kzsfTfvw rhIw== X-Gm-Message-State: AOAM5332d9gTArLDRxf+CHBFX1YqRTf4LyVNLek+CbVoa6X+4RbnXMeJ QLi1YjkyHxY8hCLglz3ajUall3jv0aCjVl+mChMinOQNoJCE0LFkuEY= X-Google-Smtp-Source: ABdhPJyKLQzFRtC14K4PnXh0rExGdZtyqz4P1QJb/n9dzxHB52VulB+kUdiVHJrgjZgIa747FbdfkKJY0k0JtWFpBng= X-Received: by 2002:ae9:c015:: with SMTP id u21mr9432400qkk.205.1629293280895; Wed, 18 Aug 2021 06:28:00 -0700 (PDT) MIME-Version: 1.0 References: <7DA18959-3463-4AAE-ABE3-B9330FEE83D2@gmail.com> In-Reply-To: Date: Wed, 18 Aug 2021 14:27:49 +0100 Message-ID: To: PHP internals Content-Type: multipart/alternative; boundary="0000000000003e272b05c9d56703" Subject: Re: [PHP-DEV] Re: [RFC] Add parse_query_string as an alternative to parse_str From: tekiela246@gmail.com (Kamil Tekiela) --0000000000003e272b05c9d56703 Content-Type: text/plain; charset="UTF-8" Hi Internals, During my research into this topic, I discovered that there exists a multibyte variant of this function in mbstring extension. This raises the question: should we add a corresponding multibyte variant of http_parse_query() to mbstring? Is there any usage in the wild of mb_parse_str()? I have even asked a question on Stack Overflow about this topic https://stackoverflow.com/questions/68761695/can-mb-parse-str-produce-different-results-than-parse-str To me, it doesn't look like parse_str() is useful anymore, but I come from Europe where things happen mostly using a single encoding. I am not aware of any problems that parse_str() might have when it comes to multiple encoding types. In fact, when looking at the whole input/output encoding feature of mbstring I am getting a feeling that this is some niche feature that almost nobody ever uses. While mbstring is useful for dealing with different encodings, I am not sure if it is common for HTTP requests to be encoded with anything else than UTF-8. I would appreciate some input from experts who know more about mbstring and encodings. Regards, Kamil > --0000000000003e272b05c9d56703--