Yeah, I read that and I will talk to my co-admin about it. Thanks!
On Fri, Nov 29, 2019 at 10:43 AM M. Manna <manme...@gmail.com> wrote: > To clarify (along with my last reply) - what you are trying to do is not > correct. The tomcat documentation confirms that only the following are > allowed > > The HTTP/1.1 specification <https://tools.ietf.org/rfc/rfc7230.txt> > requires > > that certain characters are %nn encoded when used in URI query strings. > > Unfortunately, many user agents including all the major browsers are not > > compliant with this specification and use these characters in unencoded > > form. To prevent Tomcat rejecting such requests, this attribute may be > used > > to specify the additional characters to allow. If not specified, no > > additional characters will be allowed. The value may be any combination > of > > the following characters: " < > [ \ ] ^ ` { | } . Any other characters > > present in the value will be ignored. > > > On Fri, 29 Nov 2019 at 15:39, M. Manna <manme...@gmail.com> wrote: > > > Robert, > > > > On Fri, 29 Nov 2019 at 15:28, Robert Hicks <robert.hi...@gmail.com> > wrote: > > > >> What is the correct format? > >> > >> I see the following used when I do a search: > >> > >> relaxedQueryChars="[,],{,}.|" > >> > >> relaxedQueryChars="[ ] { } |" > >> > >> relaxedQueryChars="[]|{}^\`"<>" > >> > >> We use that last one. I am running down this error: > >> > >> java.lang.IllegalArgumentException: Invalid character found in the > >> request target. The valid characters are defined in RFC 7230 and RFC > >> 3986 > >> > >> Thanks! > >> > >> -- > >> > >> > > This is a working version in Http11AprProtocol > > > > relaxedQueryChars="{[,:]|}" > > > > > > > > > >> Bob > >> > > >
