he same servlet on another servlet machine I had
> no problems !
>
>
>
> -Original Message-
> From: Alan Stenhouse
> [mailto:[EMAIL PROTECTED]]
> Sent: Mon, March 05, 2001 2:26 PM
> To: [EMAIL PROTECTED]
> Cc: [EMAIL PROTECTED]
> Subject: AW: se
[EMAIL PROTECTED]
> 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?para
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
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
> -Ursprüngliche Nachricht-
>
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 PROTECTE
that comes after 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 PROTECT
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 ChemInform
they
are directly 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 ?
Conceptual
no value
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
27;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 a XMLHTTPRequest set to "POST"), it works fine.
Seem
This works perfectty 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". I
ache.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 and submitting a form. Doing something
like 'action = <%= response.encodeURL("findnaics.jsp") %>' doesn'
);
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 was
standard. BTW, I'm
f 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
--
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 my example.
---
Bill Faulk
[EMAIL PROTECTED]
801-302-8930
-Original Message-
From: Tim Funk [
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 describe
ding 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 and submitting a form. Doing something
like 'action = <%= response.encodeURL("findnaics.jsp")
ink
that you'll 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(), &quo
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 librar
> Example:
>
> URL = "http://my.domain/some_form.htm";;
> response.sendRedirect(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 pred
t; contained 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 cr
ributes you have stored in the current session that indicate
> >what the user will be supplying.
>
> But what happens if you really do not know what character set to expect ? In
> our company, the webserver is used for B2B messaging with customers and not
> purely serving
ipart/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 such as application/url-encoded). You can't just
ine is actually generating the error if the
parameter 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" becau
;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'
actually did intend 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 paramet
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 w
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 an
t
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 query string because of their length limitation.
Thanks for any thoughts...
David
-
ave
> > >stored in the current session that indicate what the user will be
> > >supplying.
> >
> > But what happens if you really do not know what character set to
> > expect ? In our company, the webserver is used for B2B
> messaging with
> > c
:
- 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
7;t send them at all?
> >>
> >>I actually did intend 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?
> >>
> >
x27;;'
> > rather
> > > than '?' when an URL gets encoded?
> > >
> > > Example:
> > >
> > > URL = "http://my.domain/some_form.htm";;
> > >
> >
> response.sendRedirect(response.encodeRedirectURL(URL));
> > >
> >
y
> - 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 an active session will create a new
> session.
> - It's quite easy to create me
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 query string because of their length limitation.
>
> Thanks for any thoughts...
> David
>
> --
looks at incoming requests and decides what
> > > >encoding should be used -- perhaps by looking at the
> > > >Accept-Language header, or based on
> > attributes you have
> > > >stored in the current session that indicate what the user will be
> > > &g
Hainburgerstr. 33
> > Tel.: +43/1/931012/3277, Mobil: +43/650/6503277
> >
> >
> >
> > On Sat, 2 Jun 2001, Charles Baker wrote:
> >
> > > I've been browsing the archives but still haven't
> > seen
> > > what I'm looking fo
; I've been browsing the archives but still
> haven't
> > > seen
> > > > what I'm looking for. Why does Tomcat use ';'
> > > rather
> > > > than '?' when an URL gets encoded?
> > > >
> > > > Example:
> > &
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: Allistai
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
nt
* contains the username that is being presented for authentication.
*
* The distinguished name can be represented by a pattern passed to
* an instance of MessageFormat, where the string "{0}"
* in the pattern is replaced by the username being
on the data structure in the
> * underlying directory server:
> *
> * Each user that can be authenticated is represented by an individual
> * element in the top level DirContext that is accessed
> * via the connectionURL property. This element has the
> * follo
42 matches
Mail list logo
