In order to compatible with more scenarios,can we be customize the parameter SAFEQUERYSTRINGCHARS_URLENCODER?

Open
#1,780 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
api

Research direction

Start by locating SAFEQUERYSTRINGCHARS_URLENCODER and the URI query-string encoding path in the Java client. Review how semicolons are handled against RFC 3986 and the differing W3C behavior described here; done means a supported customization path is defined and covered for the reported request scenario.

Written by the indexing model from the issue text.

Description

type: feature request

SAFEQUERYSTRINGCHARS_URLENCODER: A string of characters that do not need to be encoded when used in URI query strings, as specified in RFC 3986. Note that some of these characters do need to be escaped when used in other parts of the URI.

when the server framework complies with old and new W3C specifications which are different. When the request contains "; ", Google-http-java-client does not escape it, but the server does.

In order to compatible with more scenarios,can we be customize the parameter SAFEQUERYSTRINGCHARS_URLENCODER?

Dominant language
Java
Stars
1.4k
Forks
476
Avg merge
10h 47m
Merged PRs (30d)
3

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from googleapis/google-http-java-client

All issues in googleapis/google-http-java-client

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.