[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799922#comment-17799922
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:50 PM:
---
[~exceptionfactory] That is what exactly I have done except I called the
utility class UriUtils. Do I have to mention in the UrlUtils class where I got
the regular expressions or is it enough the change to the NOTICE file stating
that there are derived works from
https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/util/UriComponentsBuilder.java
?
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what exactly I have done. Do I have to mention in
the UrlUtils class where I got the regular expressions or is it enough the
change to the NOTICE file stating that there are derived works from
https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/util/UriComponentsBuilder.java
?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799922#comment-17799922
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:49 PM:
---
[~exceptionfactory] That is what exactly I have done. Do I have to mention in
the UrlUtils class where I got the regular expressions or is it enough the
change to the NOTICE file stating that there are derived works from
https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/util/UriComponentsBuilder.java
?
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what exactly I have done. Do I have to mention in
the UrlUtils class where I got the regular expressions or is enough the change
to the NOTICE file stating that there are derived works from
https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/util/UriComponentsBuilder.java
?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:45 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using 'URI.create' would pose a problem since there
may be unquoted/unescaped characters in its query and/or fragments sections? I
am not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] and all those places in the
code which use StandardValidators#URL_VALIDATOR need this change similar to
InvokeHttp since they may not have any characters which need to be
quoted/escaped. I am not familiar enough with the form of URLs these components
use, Please advise. Thanks!
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using 'URI.create' would pose a problem since there
may be unquoted/unescaped characters in its query and/or fragments sections? I
am not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] and all
those places in the code which use StandardValidators#URL_VALIDATOR need this
change similar to InvokeHttp since they may not have any characters which need
to be quoted/escaped. I am not familiar enough with the form of URLs these
components use, Please advise. Thanks!
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:45 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using 'URI.create' would pose a problem since there
may be unquoted/unescaped characters in its query and/or fragments sections? I
am not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] and all
those places in the code which use StandardValidators#URL_VALIDATOR need this
change similar to InvokeHttp since they may not have any characters which need
to be quoted/escaped. I am not familiar enough with the form of URLs these
components use, Please advise. Thanks!
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using 'URI.create' would pose a problem since there
may be unquoted/unescaped characters in its query and/or fragments sections? I
am not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
Do all those places in the code which use StandardValidators#URL_VALIDATOR need
this change similar to InvokeHttp. I am not familiar enough with the form of
URLs these components use, Please advise. Thanks!
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:44 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using 'URI.create' would pose a problem since there
may be unquoted/unescaped characters in its query and/or fragments sections? I
am not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
Do all those places in the code which use StandardValidators#URL_VALIDATOR need
this change similar to InvokeHttp. I am not familiar enough with the form of
URLs these components use, Please advise. Thanks!
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there may
be unquoted/unescaped characters in its query and/or fragments sections? I am
not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
Do all those places in the code which use StandardValidators#URL_VALIDATOR need
this change similar to InvokeHttp. I am not familiar enough with the form of
URLs these components use, Please advise. Thanks!
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:43 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there may
be unquoted/unescaped characters in its query and/or fragments sections? I am
not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
Do all those places in the code which use StandardValidators#URL_VALIDATOR need
this change similar to InvokeHttp. I am not familiar enough with the form of
URLs these components use, Please advise. Thanks!
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there may
be unquoted/unescaped characters in its query and/or fragments sections? I am
not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped. Please advise.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:41 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there may
be unquoted/unescaped characters in its query and/or fragments sections? I am
not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped. Please advise.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there may
be unquoted/unescaped characters in its query and/or fragments sections? I am
not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:41 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there may
be unquoted/unescaped characters in its query and/or fragments sections? I am
not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there
maybe unquoted/unescaped characters in its query and/or fragments sections? I
am not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:41 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there
maybe unquoted/unescaped characters in its query and/or fragments sections? I
am not sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there be
unquoted/unescaped characters in its query and/or fragments sections? I am not
sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:40 PM:
---
[~exceptionfactory] [~pvillard] I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there be
unquoted/unescaped characters in its query and/or fragments sections? I am not
sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] So I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there be
unquoted/unescaped characters in its query and/or fragments sections? I am not
sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:39 PM:
---
[~exceptionfactory] [~pvillard] So I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there be
unquoted/unescaped characters in its query and/or fragments sections? I am not
sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this since they may not
have any characters which need to be quoted/escaped.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] So I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there be
unquoted/unescaped characters in its query and/or fragments sections? I am not
sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799917#comment-17799917
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:39 PM:
---
[~exceptionfactory] [~pvillard] So I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there be
unquoted/unescaped characters in its query and/or fragments sections? I am not
sure all of the places changed in
[#7771|https://github.com/apache/nifi/pull/7771] need this.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard] So I have developed a utility method which now
uses a regular expression to parse the 7 parts of the URI and instantiates a
URI object with those seven pieces as I had suggested earlier. I modified the
StandardValidators#URL_VALIDATOR and InvokeHttp (when creating the java.net.URI
object from the value entered in the 'HTTP_URL' property) to now use the
utility method. My question is where else would this change apply? What other
places that are currently using URI.create would pose a problem since there be
unquoted/unescaped characters in its query and/or fragments sections? I am not
sure all of the places changed in #7771 need this.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799845#comment-17799845
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:16 PM:
---
[~exceptionfactory] [~pvillard]
I am still working out the regular expression. In the meantime there is a
workaround for at least InvokeHttp. For the 'HTTP URL' property use NIFI
Expression Language and before the InvokeHttp processor use an UpdateAttribute
processor to set an attribute with the value of getUri from the NIFI Expression
Language. The value with the URL specified in the description would like
{code:java}
${getUri('https', null, 'en.wikipedia.org', -1, '/w/api.php',
'action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags',
null)}
{code}
Another option is to escape/quote by hand any illegal character(s) found in the
query and/or fragment sections of the URL. See the [URI
javadocs|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/net/URI.html]
for more details.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard]
I am still working out the regular expression. In the meantime there is a
workaround for at least InvokeHttp. For the 'HTTP URL' property use NIFI
Expression Language and before the InvokeHttp processor use an UpdateAttribute
processor to set an attribute with the value of getUri from the NIFI Expression
Language. The value with the URL specified in the description would like
{code:java}
${getUri('https', null, 'en.wikipedia.org', -1, '/w/api.php',
'action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags',
null)}
{code}
Another option is to escape/quote by hand any illegal character(s) found in the
query and/or fragment sections of the URI. See the [URI
javadocs|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/net/URI.html]
for more details.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799845#comment-17799845
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 7:15 PM:
---
[~exceptionfactory] [~pvillard]
I am still working out the regular expression. In the meantime there is a
workaround for at least InvokeHttp. For the 'HTTP URL' property use NIFI
Expression Language and before the InvokeHttp processor use an UpdateAttribute
processor to set an attribute with the value of getUri from the NIFI Expression
Language. The value with the URL specified in the description would like
{code:java}
${getUri('https', null, 'en.wikipedia.org', -1, '/w/api.php',
'action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags',
null)}
{code}
Another option is to escape/quote by hand any illegal character(s) found in the
query and/or fragment sections of the URI. See the [URI
javadocs|https://docs.oracle.com/en/java/javase/21/docs/api/java.base/java/net/URI.html]
for more details.
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard]
I am still working out the regular expression. In the meantime there is a
workaround for at least InvokeHttp. For the 'HTTP URL' property use NIFI
Expression Language and before the InvokeHttp processor use an UpdateAttribute
processor to set an attribute with the value of getUri from the NIFI Expression
Language. The value with the URL specified in the description would like
{code:java}
${getUri('https', null, 'en.wikipedia.org', -1, '/w/api.php',
'action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags',
null)}
{code}
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799863#comment-17799863
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 3:46 PM:
---
[~exceptionfactory] I found the following [Stackoverflow
Post|https://stackoverflow.com/questions/60324474/how-to-parse-any-url-uri-in-java]
where the question seems to have had the exact problem in the description of
this ticket (i.e. the part about URI construction failing when there are
illegal characters). The suggestion in that post is the use of Spring's
[UriComponentsBuilder|https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/util/UriComponentsBuilder.java].
The questioner responded
??If you are on a non-Spring application the library
org.springframework:spring-web and it's dependencies are a big bunch of code
(~3.4MB at the moment for 5.2.3) just for parsing URIs. But the Regex pattern
URI_PATTERN in the linked code and the fromUriString(String) method seems to be
of great value. And it is under Apache 2 license??
If its under Apache License can we take advantage of the code in a different
form as the questioner seemed to imply? He is right the Regex pattern
URI_PATTERN in the linked code and the fromUriString(String) method seems to be
of great value.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found the following [Stackoverflow
Post|https://stackoverflow.com/questions/60324474/how-to-parse-any-url-uri-in-java]
where the question seems to be the exact problem in the description of this
ticket (i.e. the part about URI construction failing when there are illegal
characters). The suggestion in that post is the use of Spring's
[UriComponentsBuilder|https://github.com/spring-projects/spring-framework/blob/main/spring-web/src/main/java/org/springframework/web/util/UriComponentsBuilder.java].
The questioner responded
??If you are on a non-Spring application the library
org.springframework:spring-web and it's dependencies are a big bunch of code
(~3.4MB at the moment for 5.2.3) just for parsing URIs. But the Regex pattern
URI_PATTERN in the linked code and the fromUriString(String) method seems to be
of great value. And it is under Apache 2 license??
If its under Apache License can we take advantage of the code in a different
form as the questioner seemed to imply? He is right the Regex pattern
URI_PATTERN in the linked code and the fromUriString(String) method seems to be
of great value.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799845#comment-17799845
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/22/23 2:10 PM:
---
[~exceptionfactory] [~pvillard]
I am still working out the regular expression. In the meantime there is a
workaround for at least InvokeHttp. For the 'HTTP URL' property use NIFI
Expression Language and before the InvokeHttp processor use an UpdateAttribute
processor to set an attribute with the value of getUri from the NIFI Expression
Language. The value with the URL specified in the description would like
{code:java}
${getUri('https', null, 'en.wikipedia.org', -1, '/w/api.php',
'action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags',
null)}
{code}
was (Author: JIRAUSER294662):
[~exceptionfactory] [~pvillard]
I am still working out the regular expression. In the meantime there is a
workaround for at least InvokeHttp. For the 'HTTP URL' property use NIFI
Expression Language and before the InvokeHttp use UpdateAttribute to set an
attribute with the value of getUri from the NIFI Expression Language. The value
with the URL specified in the description would like
{code:java}
${getUri('https', null, 'en.wikipedia.org', -1, '/w/api.php',
'action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags',
null)}
{code}
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:09 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.??
??9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoded) as
the Javadoc uses the word "quoted".
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.??
??9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:08 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.??
??9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:06 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:07 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??
8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:07 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)].
??
8. If a query is given then a question-mark character ('?') is appended,
followed by the query. Any character that is not a legal URI character is
quoted.
9. Finally, if a fragment is given then a hash character ('#') is appended,
followed by the fragment. Any character that is not a legal URI character is
quoted.
??
I think though I originally did not use the correct wording (i.e. encoding) as
the Javadoc uses the word "quoting.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:03 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query. See steps 8 and 9 on the javadocs of [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799235#comment-17799235
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/21/23 3:01 AM:
---
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query.
was (Author: JIRAUSER294662):
[~exceptionfactory] That is what I thought the URI constructor does it encodes
the path and query.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:51 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]?
The only thing I did not see was a regular expression for parsing the password
which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:51 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]?
The only thing I did not see was a regular expression for parsing the password
which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]?
The only thing I did not see was a regular expression for parsing the password
which could be part of userInfo.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:50 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
that there are regular expressions for extracting the scheme, user, host,
port, path, query and fragment sections of a URL (Chapter 8 sections 8.8 -
8.14). Couldn't we use those to extract the pieces needed for the [URI
constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:46 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of userInfo.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of user-info.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799070#comment-17799070
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/20/23 3:39 PM:
---
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
? The only thing I did not see was a regular expression for parsing the
password which could be part of user-info.
was (Author: JIRAUSER294662):
[~exceptionfactory] I found in [Regular Expressions Cookbook 2nd
Edition|https://doc.lagout.org/programmation/Regular%20Expressions/Regular%20Expressions%20Cookbook_%20Detailed%20Solutions%20in%20Eight%20Programming%20Languages%20%282nd%20ed.%29%20%5BGoyvaerts%20%26%20Levithan%202012-09-06%5D.pdf]
there are regular expressions for extracting the scheme, user, host, port,
path, query and fragment sections of a URL (Chapter 8 sections 8.8 - 8.14).
Couldn't we use those to extract the pieces needed for the [URI constructor
|https://docs.oracle.com/en/java/javase/21/docs//api/java.base/java/net/URI.html#%3Cinit%3E(java.lang.String,java.lang.String,java.lang.String,int,java.lang.String,java.lang.String,java.lang.String)]
?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798372#comment-17798372
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 10:32 PM:
Looks like a lot of low level parsing found in
[URLStreamHandler#parseURL|https://github.com/openjdk/jdk21/blob/890adb6410dab4606a4f26a942aed02fb2f55387/src/java.base/share/classes/java/net/URLStreamHandler.java#L138]
was (Author: JIRAUSER294662):
Looks like a lot of low level parsing found
[URLStreamHandler#parseURL|https://github.com/openjdk/jdk21/blob/890adb6410dab4606a4f26a942aed02fb2f55387/src/java.base/share/classes/java/net/URLStreamHandler.java#L138]
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798356#comment-17798356
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:59 PM:
---
FYI I got this to work
{code:java}
String scheme = "https";
String userInfo = null;
String host = "en.wikipedia.org";
int port = -1;
String path = "/w/api.php";
String query =
"action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags";
String fragment = null;
URI uri = new URI(scheme, userInfo, host, port, path, query, fragment);
{code}
was (Author: JIRAUSER294662):
FYI I got this to work
{code:java}
String scheme = "https";
String userInfo = null;
String host = "en.wikipedia.org";
int port = -1;
String path = "/w/api.php";
String query =
"action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags";
String fragment = null;
URI uri = new URI(scheme, userInfo, host, port, path, query, fragment);
{code}
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:37 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-int-java.lang.String-java.lang.String-java.lang.String-]]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [[URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-int-java.lang.String-java.lang.String-java.lang.String-]]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:37 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-int-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-int-java.lang.String-java.lang.String-java.lang.String-]]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:36 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [[URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-int-java.lang.String-java.lang.String-java.lang.String-]]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [[URI
constructor|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-int-java.lang.String-java.lang.String-java.lang.String-]
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:35 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [[URI
constructor|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-int-java.lang.String-java.lang.String-java.lang.String-]
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:22 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object?
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:20 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI. Could we wrap the use of this API in a
utility method and then use it in StandardValidators.URL_VALIDATOR and all the
classes which require parsing a URL to a java.netURL / java.net.URI object.
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:18 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) which can handle parsing the components and convert
it to a java.netURL / java.net.URI
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) it can handle parsing the components and convert it
to a java.netURL / java.net.URI
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:17 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need to parse the user entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) it can handle parsing the components and convert it
to a java.netURL / java.net.URI
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need code to parse the entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) it can handle parsing the components and convert it
to a java.netURL / java.net.URI
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:16 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need code to parse the entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) it can handle parsing the components and convert it
to a java.netURL / java.net.URI
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the [link title|http://example.com]URL you
listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need code to parse the entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) it can handle parsing the components and convert it
to a java.netURL / java.net.URI
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:15 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the [link title|http://example.com]URL you
listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
I found this [Stackoverflow
post|https://stackoverflow.com/questions/75966165/how-to-replace-the-deprecated-url-constructors-in-java-20]
helpful understanding that the issue is probably an encoding issue. I think
using this [URI constructor
|https://docs.oracle.com/javase/8/docs/api/java/net/URI.html#URI-java.lang.String-java.lang.String-java.lang.String-java.lang.String-java.lang.String-]would
help as it would identify which parts needs to be encoded (escaped). The issue
though is we would need code to parse the entered URL to identify its
components. I found the following [API|https://github.com/smola/galimatias]
(though its a little old) it can handle parsing the components and convert it
to a java.netURL / java.net.URI
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (NIFI-12513) Regression in InvokeHTTP - Not a valid URL
[
https://issues.apache.org/jira/browse/NIFI-12513?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17798343#comment-17798343
]
Daniel Stieglitz edited comment on NIFI-12513 at 12/18/23 8:00 PM:
---
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but any PropertyDescriptor which uses
the StandardValidators.URL_VALIDATOR will fail to validate.
was (Author: JIRAUSER294662):
[~pvillard] It would seem this issue is not specific to InvokeHttp but with the
StandardValidators.URL_VALIDATOR as the URL you listed fails when called with
{code:java}
URI.create(evaluatedInput).toURL();{code}
The same logic is called in InvokeHTTP but anything PropertyDescriptor which
uses the StandardValidators.URL_VALIDATOR will fail to validate.
> Regression in InvokeHTTP - Not a valid URL
> --
>
> Key: NIFI-12513
> URL: https://issues.apache.org/jira/browse/NIFI-12513
> Project: Apache NiFi
> Issue Type: Bug
> Components: Extensions
>Affects Versions: 2.0.0-M1, 1.24.0
>Reporter: Pierre Villard
>Assignee: Daniel Stieglitz
>Priority: Major
>
> On NiFi 1.24 and NiFi 2.0-M1, the below URL
> {code:java}
> https://en.wikipedia.org/w/api.php?action=query=recentchanges=json=user|comment|parsedcomment|timestamp|title|sizes|tags{code}
> Is no longer considered as valid but it was a valid one before.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
