The # character is a special character in URLs to signify a "fragment":  
https://en.wikipedia.org/wiki/Fragment_identifier.  If you don't want it 
treated as such then you do need to escape it.

-Dave

Dave Tauzell | Senior Software Engineer | Surescripts
O: 651.855.3042 | www.surescripts.com |   [email protected]
Connect with us: Twitter I LinkedIn I Facebook I YouTube


-----Original Message-----
From: Ben Mazyopa [mailto:[email protected]]
Sent: Monday, November 30, 2015 9:15 AM
To: [email protected]
Subject: Re: Hash (#) error in Parameters value

Dear Team,

I am a devote user of tomcat servers, however I have met a bug when using 
Apache Tomcat 7.0.52, on Windows 10 64bit. Whenever I pass a parameter value of 
# or *214#, the parameter value ends up being null.

For example when I navigate to "http://localhost:8080/myapp/demo?param=*214#";
param value will be null if I try to access it in a servlet (for exam 
request.getParameter("param")). However if I pass a different value, the value 
is retreived correctly.

May you kindly fix the bug, rather forcing users and developers to pass unicode 
values for a hash eg. *214%23)

Your response and action will be appreciated

Regards
Ben Mazyopa

On Mon, Nov 30, 2015 at 4:14 PM, Ben Mazyopa <[email protected]> wrote:

> Dear Team,
>
> I am a devote user of tomcat servers, however I have met a bug when
> using Apache Tomcat 7.0.52, on Windows 10 64bit. Whenever I pass a
> parameter value of # or *214#, the parameter value ends up being null.
>
> For example when I navigate to "
> http://localhost:8080/myapp/demo?param=*214#"; param value will be null
> if I try to access it in a servlet (for exam request.getParameter("param")).
> However if I pass a different value, the value is retreived correctly.
>
> May you kindly fix the bug, rather forcing users and developers to
> pass unicode values for a hash eg. *214%23)
>
> Your response and action will be appreciated
>
> Regards
> Ben Mazyopa
>
This e-mail and any files transmitted with it are confidential, may contain 
sensitive information, and are intended solely for the use of the individual or 
entity to whom they are addressed. If you have received this e-mail in error, 
please notify the sender by reply e-mail immediately and destroy all copies of 
the e-mail and any attachments.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to