According to RFC2396, '+' is are reserved character in the
query string, but not in the path portion of a URL. There
was a bug fix in Tomcat 3.3.1 to avoid translating '+'
to ' ' in the parts of the URL prior to the query string.
Cheers,
Larry
-Original Message-
From: Olaf Vetter
paramValue)
when passing the parameter.
i.e. ensure that it's encoded correctly...
HTH
Alan
-Ursprngliche Nachricht-
Von: shlomi sarfati [mailto:[EMAIL PROTECTED]]
Gesendet: Montag, 5. Mrz 2001 12:55
An: [EMAIL PROTECTED]
Betreff: servlet Query string
Hi every one
]
Betreff: servlet Query string
Hi every one
I have a problem in my servlets.
when someone sends parameters through the query string to my
servlet that
have the character '%'
in it , something like: myservlet?param=fh%fjnv I cannot receive the
parameter in my servlet
I know that there i
the servlet path but before the query
string in the request URL; or null if the URL does not have any extra
path information
Decoded is the key word above.
Yoav Shapira http://www.yoavshapira.com
-Original Message-
From: Garret Wilson [mailto:[EMAIL PROTECTED]
Sent: Tuesday, December 07, 2004 9
testing and it is clear that the parameters are not
decoded correctly if the parameters are passed in using the query
string, or from a form with method=GET. If using method=POST (or
using a XMLHTTPRequest set to POST), it works fine.
Seems like a bug to me, or am I missing something.
Nick
on OC4J and now I have
deployed the app to Jonas (which has tomcat 5.0.28 integrated).
I've done some testing and it is clear that the parameters are not
decoded correctly if the parameters are passed in using the query
string, or from a form with method=GET. If using method=POST (or
using
So, I still see it as a problem with the use of an expression
as the attribute value in a custom taglib tag.
Kevin HaleBoyes
From: Craig R. McClanahan
I just answered this in the bug report, but will answer here as well
since
it's been raised here.
Request URIs (including the query string
05, 2001 2:26 PM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: AW: servlet Query string
you must use
"param" + URLEncoder.encode(paramValue)
when passing the parameter.
i.e. ensure that it's encoded correctly...
HTH
Alan
-Ursprngliche Nachricht-
Von: shlomi sarfa
substitutable from various references around the internet.
But your comments imply otherwise.
I'd be happy to lookup path params in the same way I do for query
string params with a call:
value = request.getPathParameter(name);
Can I do this ?
Conceptually what is the difference between
Howdy,
You are responsible for URL-encoding the query string.
Passing it on the query string is not that good an idea anyways because
of the limited length. You're better off passing it as a request
parameter (still URL-encoded) in a POST request.
Yoav Shapira
Millennium ChemInformatics
request.getInputStream(). Normally they are encoded in the same
way as the query string (unless you change the enctype on the form).
This isn't a bug.
[EMAIL PROTECTED] on 30/01/2001 04:18:59
Please respond to [EMAIL PROTECTED]; Please respond to
[EMAIL PROTECTED]
To: [EMAIL PROTECTED]
cc
/some_form.htm;jsessionid=lidfano10
and a 404 not found error.
I use JRun at work because my company is predjudiced
against free software, and it uses the '?' to separate
the url and the query string which I thought was
standard. BTW, I'm using Tomcat 3.2.1 and Apache
1.3.14 on Mandrake 7.2. I saw some
Hi FTP (nice name),
multipart/form-data doesn't send the value as query string parameters (not a
normal post such as application/url-encoded). You can't just do a
request.getParameter(someparameter) for a multipart/form-data POST.
Try checking out various file upload libraries (oreilly.com has
in using the query
string, or from a form with method=GET. If using method=POST (or
using a XMLHTTPRequest set to POST), it works fine.
Seems like a bug to me, or am I missing something.
Nick
-
To unsubscribe, e-mail: [EMAIL
Why don't you use: http://website/findnaics.jsp?code=%25
-Tim
Bill Faulk wrote:
I am using Tomcat 4.1.29 on Windows 2000 Server with Java SDK 1.4.2.
On the user query forms in my application % is a valid wildcard for
all as it is in the actual database query. I don't want to use blank
for all
get a properly converted string out but you don't.
Node.getNodeValue() gives you a String that contains bytes that are
still UTF-8 encoded! You have to do this to get 'em into a real Java
String:
String newCN = new String(query.getCommonName().getBytes(), "UTF-8");
As I clean th
contains a %.
String code = request.getParameter(code);
I've seen this error when searching in regards to forwarding pages
(http://nagoya.apache.org/bugzilla/show_bug.cgi?id=3986) but it was
considered invalid because forward expects an encoded url. However,
I am simply passing a parameter
There looks to be a patch against this region of code in 4.1.30. (As compared
to 4.1.29) Does the same thing happen there?
-Tim
Bill Faulk wrote:
The same error occurs for %25. If I put a % anywhere in the
parameter I get a crash. 4% would pass a parameter to query everything
starting with 4
in parameter
value
There looks to be a patch against this region of code in 4.1.30. (As
compared
to 4.1.29) Does the same thing happen there?
-Tim
Bill Faulk wrote:
The same error occurs for %25. If I put a % anywhere in the
parameter I get a crash. 4% would pass a parameter to query
everything
character set to expect ? In
our company, the webserver is used for B2B messaging with customers and not
purely serving web pages. For example, we can accept a message with a query
string like this
http://vpn.ourcompany.com/servlet/incoming?company=CustomerNamereferenceId=1234noteText
www.host.com
resides).
I don't think that an encrypted, base64 encoded authentication piece will
fit in a standard URL query string because of their length limitation.
Thanks for any thoughts...
David
-
To unsubscribe, e-ma
Are you working with cookies or url rewriting?
You have to keep some facts in mind:
- each session needs some memory
- each session will be alive some time after the last
request to the session (default: 30 Minutes)
- each request without a cookie or an encoded Url that
matches
-data is requested!!! I didn't try the
oreilly.com one but does this behave in a different way?
Thanks
Hi FTP (nice name),
multipart/form-data doesn't send the value as query string parameters (not a
normal post such as application/url-encoded). You can't just do a
request.getParameter
to use the apache file-upload and got into this
problem cause multipart/form-data is requested!!! I didn't try the
oreilly.com one but does this behave in a different way?
Thanks
Hi FTP (nice name),
multipart/form-data doesn't send the value as query string parameters
(not a normal post
:
- Parameters in the query string
- Servlet paths
There is a standard for encoding URIs
(http://www.w3.org/International/O-URL-code.html) but this standard is not
consistently followed by clients. This causes a number of problems.
The functionality provided by Tomcat (4 and 5) to handle this less than
I just answered this in the bug report, but will answer here as well since
it's been raised here.
Request URIs (including the query string) processed by servlet containers
must conform to the requirements of HTTP. In this case, the relevant spec
is RFC 2396, Section 3.2, which describes
expects an encoded url. However, I
am simply passing a parameter and submitting a form. Doing something
like 'action = %= response.encodeURL(findnaics.jsp) %' doesn't do
anything for me. Using quotes/backslash, etc. doesn't make any
difference. These query parameters can be passed by both GET and POST so
with a query string like this
http://vpn.ourcompany.com/servlet/incoming? company=CustomerNamerefere
nceId=1234noteText=
The noteText could be in one of several languages since we do
international business. We're currently considering adding
a language
parameter such as Language=English
(response.encodeRedirectURL(URL));
Yeilds an url like this:
http://my.domain/some_form.htm;jsessionid=lidfano10
and a 404 not found error.
I use JRun at work because my company is
predjudiced
against free software, and it uses the '?' to
separate
the url and the query string which I thought
and a 404 not found error.
I use JRun at work because my company is
predjudiced
against free software, and it uses the '?' to
separate
the url and the query string which I thought was
standard. BTW, I'm using Tomcat 3.2.1 and Apache
1.3.14 on Mandrake 7.2. I saw some workarounds
software, and it uses the '?' to
separate
the url and the query string which I thought
was
standard.
SNIP
=
-
[EMAIL PROTECTED]
Hacking is a Good Thing!
See http://www.tuxedo.org/~esr/faqs/hacker-howto.html
__
Do You Yahoo!?
Get
hat app1 can be sure that the user really
did come there from a valid logon from www.host.com (it's possible that
app1.host.com is not even in the same city as the server where www.host.com
resides).
I don't think that an encrypted, base64 encoded authentication piece will
fit in a standard URL
some time after the
last
request to the session (default: 30 Minutes)
- each request without a cookie or an encoded Url
that
matches an active session will create a new
session.
- It's quite easy to create memory leaks
(especialy with a database)
So your memory requirement
in a different way?
Thanks
Hi FTP (nice name),
multipart/form-data doesn't send the value as query string parameters
(not a normal post such as application/url-encoded). You can't just do a
request.getParameter(someparameter) for a multipart/form-data POST.
Try checking out various file upload
but does this behave in a different way?
Thanks
Hi FTP (nice name),
multipart/form-data doesn't send the value as query string parameters
(not a normal post such as application/url-encoded). You can't just do a
request.getParameter(someparameter) for a multipart/form-data POST.
Try
I don't know. The reason JNDIRealm did not work was IPlanet returns the
SHA digested password as a Base64 encoded (Mime like) string. The
(original) tomcat code takes the passsword and converts it to a Hex
string. Base64 string will never equal the Hex string.
I have no idea what MySQL
=lidfano10
and a 404 not found error.
I use JRun at work because my company is
predjudiced
against free software, and it uses the '?' to
separate
the url and the query string which I thought was
standard. BTW, I'm using Tomcat 3.2.1 and Apache
1.3.14 on Mandrake 7.2. I saw some
not know what character set to
expect ? In our company, the webserver is used for B2B
messaging with
customers and not purely serving web pages. For example, we can
accept a message with a query string like this
http://vpn.ourcompany.com/servlet/incoming? company=CustomerNamerefere
distinguished name can be represented by a pattern passed to
* an instance of codeMessageFormat/code, where the string {0}
* in the pattern is replaced by the username being presented./li
* liThe element for this user contains an attribute named by the
* codeuserPassword
/code) attribute of this
element
* contains the username that is being presented for
authentication.
* /li
* liThe distinguished name can be represented by a pattern passed
to
* an instance of codeMessageFormat/code, where the string
{0}
* in the pattern
that rather than the auth
String starting with 'NTLM' it starts with 'Negotiate' in the scenarios that
didn't work! The encoded Domain and Username where still there, so I just
retrieved them as well.
Thanks for your reply
Regards
Sue
-Original Message-
From: Allistair Crossley [mailto:[EMAIL
with this problem. I assume that this is configuration
problem. But the way the Expected protocal pull down ways set to HTTP/1.0 after Submit
Query buttom was pressed. Hence, the following listing ways show the HTTP/1.0 and the
text Running test-tomcat 8080 192.168.0.126 HTTP/1.1
indicate the type
1.1 setting.
Please help me with this problem. I assume that this is
configuration problem. But the way the Expected protocal pull
down ways set to HTTP/1.0 after Submit Query buttom was
pressed. Hence, the following listing ways show the HTTP/1.0
and the text Running test-tomcat 8080
43 matches
Mail list logo
