[jira] [Created] (HTTPCORE-745) ContentType.create(String, NameValuePair...) should make a defensive copy of its input array

Gary D. Gregory created HTTPCORE-745: Summary: ContentType.create(String, NameValuePair...) should make a defensive copy of its input array Key: HTTPCORE-745 URL: https://issues.apache.org/jira/browse/HTTPCORE

[GitHub] [httpcomponents-core] garydgregory opened a new pull request, #404: [HTTPCORE-745] ContentType.create(String, NameValuePair...) defensive copy

garydgregory opened a new pull request, #404: URL: https://github.com/apache/httpcomponents-core/pull/404 [HTTPCORE-745] ContentType.create(String, NameValuePair...) should make a defensive copy of its input array -- This is an automated message from the Apache Git Service. To respond to

[jira] [Updated] (HTTPCORE-745) ContentType.create(String, NameValuePair...) should make a defensive copy of its input array

[ https://issues.apache.org/jira/browse/HTTPCORE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated HTTPCORE-745: - External issue URL: https://github.com/apache/httpcomponents-core/pull/404 > ContentTyp

[jira] [Updated] (HTTPCORE-745) ContentType.create(String, NameValuePair...) should make a defensive copy of its input array

[ https://issues.apache.org/jira/browse/HTTPCORE-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gary D. Gregory updated HTTPCORE-745: - Description: The factory method {{ContentType.create(String, NameValuePair...)}} should

[jira] [Commented] (HTTPCLIENT-2159) Invalid handling of charset content type parameter

[ https://issues.apache.org/jira/browse/HTTPCLIENT-2159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17718569#comment-17718569 ] Gary D. Gregory commented on HTTPCLIENT-2159: - WRT ContentType it sounds

[GitHub] [httpcomponents-core] michael-o commented on a diff in pull request #404: [HTTPCORE-745] ContentType.create(String, NameValuePair...) defensive copy

michael-o commented on code in PR #404: URL: https://github.com/apache/httpcomponents-core/pull/404#discussion_r1182553606 ## httpcore5/src/main/java/org/apache/hc/core5/http/ContentType.java: ## @@ -378,7 +378,7 @@ private static ContentType create(final String mimeType, fina

[GitHub] [httpcomponents-core] garydgregory commented on a diff in pull request #404: [HTTPCORE-745] ContentType.create(String, NameValuePair...) defensive copy

garydgregory commented on code in PR #404: URL: https://github.com/apache/httpcomponents-core/pull/404#discussion_r1182562924 ## httpcore5/src/main/java/org/apache/hc/core5/http/ContentType.java: ## @@ -378,7 +378,7 @@ private static ContentType create(final String mimeType, f

[GitHub] [httpcomponents-client] arturobernalg opened a new pull request, #442: Implement ExponentialBackoffManager for connection management (HTTPCLIENT-2272)

arturobernalg opened a new pull request, #442: URL: https://github.com/apache/httpcomponents-client/pull/442 This pull request addresses the issue [HTTPCLIENT-2272](https://issues.apache.org/jira/browse/HTTPCLIENT-2272) by introducing the ExponentialBackoffManager class, which enhances the

[GitHub] [httpcomponents-core] michael-o commented on a diff in pull request #404: [HTTPCORE-745] ContentType.create(String, NameValuePair...) defensive copy

michael-o commented on code in PR #404: URL: https://github.com/apache/httpcomponents-core/pull/404#discussion_r1182802070 ## httpcore5/src/main/java/org/apache/hc/core5/http/ContentType.java: ## @@ -378,7 +378,7 @@ private static ContentType create(final String mimeType, fina

[GitHub] [httpcomponents-core] garydgregory commented on a diff in pull request #404: [HTTPCORE-745] ContentType.create(String, NameValuePair...) defensive copy

garydgregory commented on code in PR #404: URL: https://github.com/apache/httpcomponents-core/pull/404#discussion_r1182826671 ## httpcore5/src/main/java/org/apache/hc/core5/http/ContentType.java: ## @@ -378,7 +378,7 @@ private static ContentType create(final String mimeType, f

Re: Parsing RFC2231 or newer spec'd data

On 2023/05/01 21:19:35 Michael Osipov wrote: > Am 2023-05-01 um 22:46 schrieb Gary Gregory: > > Well, that puts a nail in that coffin. Thank you for the details. > > BUT, you have to look into Apache James which has a decent MIME parser > which we are using at work. I would say that it is enough