URI getRawQuery vs getQuery












2















I think that using getQuery loses information, is dangerous and that instead only getRawQuery should be used, and that any query parameter values that are known to be encoded should be manually decoded (once the raw query is split on the & characters) with URLDecoder.



Case in point: Assume you have the URL www.example.com with two query parameters:




  • a parameter url with value =www.otherexample.com?b=2&c=3

  • a nondescript parameter d with value 4.


The parameter url should be url-encoded, so the URI that your application sees is:



www.example.com?url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



Now, if you obtain the query part with getQuery, you get the following:



url=www.otherexample.com?b=2&c=3&d=4



Notice that you've already lost information as you can't say whether d is a query parameter of the www.example.com or of www.otherexample.com.



If instead you obtain the query part with getRawQuery, you get the following:



url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



This time, no information is lost and all's well. You can parse the query part and URL-decode the value of the url parameter if you like.



Am I missing anything ?










share|improve this question



























    2















    I think that using getQuery loses information, is dangerous and that instead only getRawQuery should be used, and that any query parameter values that are known to be encoded should be manually decoded (once the raw query is split on the & characters) with URLDecoder.



    Case in point: Assume you have the URL www.example.com with two query parameters:




    • a parameter url with value =www.otherexample.com?b=2&c=3

    • a nondescript parameter d with value 4.


    The parameter url should be url-encoded, so the URI that your application sees is:



    www.example.com?url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



    Now, if you obtain the query part with getQuery, you get the following:



    url=www.otherexample.com?b=2&c=3&d=4



    Notice that you've already lost information as you can't say whether d is a query parameter of the www.example.com or of www.otherexample.com.



    If instead you obtain the query part with getRawQuery, you get the following:



    url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



    This time, no information is lost and all's well. You can parse the query part and URL-decode the value of the url parameter if you like.



    Am I missing anything ?










    share|improve this question

























      2












      2








      2








      I think that using getQuery loses information, is dangerous and that instead only getRawQuery should be used, and that any query parameter values that are known to be encoded should be manually decoded (once the raw query is split on the & characters) with URLDecoder.



      Case in point: Assume you have the URL www.example.com with two query parameters:




      • a parameter url with value =www.otherexample.com?b=2&c=3

      • a nondescript parameter d with value 4.


      The parameter url should be url-encoded, so the URI that your application sees is:



      www.example.com?url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



      Now, if you obtain the query part with getQuery, you get the following:



      url=www.otherexample.com?b=2&c=3&d=4



      Notice that you've already lost information as you can't say whether d is a query parameter of the www.example.com or of www.otherexample.com.



      If instead you obtain the query part with getRawQuery, you get the following:



      url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



      This time, no information is lost and all's well. You can parse the query part and URL-decode the value of the url parameter if you like.



      Am I missing anything ?










      share|improve this question














      I think that using getQuery loses information, is dangerous and that instead only getRawQuery should be used, and that any query parameter values that are known to be encoded should be manually decoded (once the raw query is split on the & characters) with URLDecoder.



      Case in point: Assume you have the URL www.example.com with two query parameters:




      • a parameter url with value =www.otherexample.com?b=2&c=3

      • a nondescript parameter d with value 4.


      The parameter url should be url-encoded, so the URI that your application sees is:



      www.example.com?url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



      Now, if you obtain the query part with getQuery, you get the following:



      url=www.otherexample.com?b=2&c=3&d=4



      Notice that you've already lost information as you can't say whether d is a query parameter of the www.example.com or of www.otherexample.com.



      If instead you obtain the query part with getRawQuery, you get the following:



      url=www%2Eotherexample%2Ecom%3Fb%3D2%26c%3D3&d=4



      This time, no information is lost and all's well. You can parse the query part and URL-decode the value of the url parameter if you like.



      Am I missing anything ?







      java uri






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Feb 13 '18 at 22:05









      Marcus Junius BrutusMarcus Junius Brutus

      11.7k19115228




      11.7k19115228
























          1 Answer
          1






          active

          oldest

          votes


















          1














          You're correct.
          URI.getQuery() is broken and you shouldn't use it.



          Strange thing is I can't find any confirmation of this apart from your post, which made me think maybe URI.getQuery could be useful for something. But after some testing of my own I'm pretty sure it just shouldn't be used unless your application's query string doesn't follow the convention of separating arguments with ampersand.






          share|improve this answer
























          • For anyone interested in what Oracle has to say, I've opened a bug report for this issue: bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214423

            – Martin
            Nov 28 '18 at 6:56











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48776437%2furi-getrawquery-vs-getquery%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          1














          You're correct.
          URI.getQuery() is broken and you shouldn't use it.



          Strange thing is I can't find any confirmation of this apart from your post, which made me think maybe URI.getQuery could be useful for something. But after some testing of my own I'm pretty sure it just shouldn't be used unless your application's query string doesn't follow the convention of separating arguments with ampersand.






          share|improve this answer
























          • For anyone interested in what Oracle has to say, I've opened a bug report for this issue: bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214423

            – Martin
            Nov 28 '18 at 6:56
















          1














          You're correct.
          URI.getQuery() is broken and you shouldn't use it.



          Strange thing is I can't find any confirmation of this apart from your post, which made me think maybe URI.getQuery could be useful for something. But after some testing of my own I'm pretty sure it just shouldn't be used unless your application's query string doesn't follow the convention of separating arguments with ampersand.






          share|improve this answer
























          • For anyone interested in what Oracle has to say, I've opened a bug report for this issue: bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214423

            – Martin
            Nov 28 '18 at 6:56














          1












          1








          1







          You're correct.
          URI.getQuery() is broken and you shouldn't use it.



          Strange thing is I can't find any confirmation of this apart from your post, which made me think maybe URI.getQuery could be useful for something. But after some testing of my own I'm pretty sure it just shouldn't be used unless your application's query string doesn't follow the convention of separating arguments with ampersand.






          share|improve this answer













          You're correct.
          URI.getQuery() is broken and you shouldn't use it.



          Strange thing is I can't find any confirmation of this apart from your post, which made me think maybe URI.getQuery could be useful for something. But after some testing of my own I'm pretty sure it just shouldn't be used unless your application's query string doesn't follow the convention of separating arguments with ampersand.







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 22 '18 at 14:16









          MartinMartin

          1,0161916




          1,0161916













          • For anyone interested in what Oracle has to say, I've opened a bug report for this issue: bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214423

            – Martin
            Nov 28 '18 at 6:56



















          • For anyone interested in what Oracle has to say, I've opened a bug report for this issue: bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214423

            – Martin
            Nov 28 '18 at 6:56

















          For anyone interested in what Oracle has to say, I've opened a bug report for this issue: bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214423

          – Martin
          Nov 28 '18 at 6:56





          For anyone interested in what Oracle has to say, I've opened a bug report for this issue: bugs.java.com/bugdatabase/view_bug.do?bug_id=JDK-8214423

          – Martin
          Nov 28 '18 at 6:56




















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48776437%2furi-getrawquery-vs-getquery%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Paul Cézanne

          UIScrollView CustomStickyHeader Resize height generates problems when scroll is too fast

          Angular material date-picker (MatDatepicker) auto completes the date on focus out