RE: [OFF-TOPIC] RE: can resultset object be re-used

2003-10-01 Thread Allen Hadden
What in the heck are you talking about?  The example code doesn't reuse a ResultSet 
object...each executeQuery call returns a new ResultSet object.

OK, now we're WAY off topic.

Allen

 -Original Message-
 From: Mike Curwen [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, October 01, 2003 9:58 AM
 To: 'Tomcat Users List'
 Subject: RE: [OFF-TOPIC] RE: can resultset object be re-used
 
 
 Well I just gotta say that's not true.  You *can* re-use a resultset
 object. 
 
 ResultSet rs = st.executeQuery(SELECT * FROM FOO);
 //code that loops over rs and outputs results...
 rs = st.executeQuery(SELECT * FROM BAR);
 //a re-used ResultSet object.
 
 
  -Original Message-
  From: Shapira, Yoav [mailto:[EMAIL PROTECTED] 
  Sent: Wednesday, October 01, 2003 7:44 AM
  To: Tomcat Users List
  Subject: [OFF-TOPIC] RE: can resultset object be re-used
  
  
  
  Howdy,
  First, this is off-topic and should be marked as such.
  
  Second, the answer is no: you can't reuse them, it's one per 
  query.  In fact, since ResultSet is an interface, you don't 
  even have a constructor you can use (although you could 
  always try to reflect the implementation).
  
  Yoav Shapira
  Millennium ChemInformatics
  
  
  -Original Message-
  From: Paul [mailto:[EMAIL PROTECTED]
  Sent: Tuesday, September 30, 2003 4:21 PM
  To: Tomcat Users List
  Subject: can resultset object be re-used
  
  jdbc question (tomcat 4.x, java 1.4.2, jdbc 3.0):
  
  can the ResultSet object be re-used to retrieve results from 
  altogether 
  different sql query in same .jsp page?  Or does a new 
  ResultSet object
  need
  to be created for each distinct sql query?
  
  -paul lomack.
  
  
  
  This e-mail, including any attachments, is a confidential 
  business communication, and may contain information that is 
  confidential, proprietary and/or privileged.  This e-mail is 
  intended only for the individual(s) to whom it is addressed, 
  and may not be saved, copied, printed, disclosed or used by 
  anyone else.  If you are not the(an) intended recipient, 
  please immediately delete this e-mail from your computer 
  system and notify the sender.  Thank you.
  
  
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
  
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Stop Tomcat Remotely

2003-09-25 Thread Allen Hadden

You can still remotely stop the Windows service, regardless of the fact that Tomcat 
only listens on localhost:8005.  The two mechanisms are completely different.  You can 
stop any Windows service using the mechanism I described.

Allen

 -Original Message-
 From: Filip Hanik [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, September 24, 2003 5:29 PM
 To: Tomcat Users List
 Subject: Re: Stop Tomcat Remotely
 
 
 I was under the impression, and this has maybe already been 
 answered, that
 because of security issues, 8005 only accepts connections 
 from the same host
 
 Filip
 - Original Message -
 From: Allen Hadden [EMAIL PROTECTED]
 To: Tomcat Users List [EMAIL PROTECTED]
 Sent: Wednesday, September 24, 2003 1:49 PM
 Subject: RE: Stop Tomcat Remotely
 
 
 
 If it's running as a Windows service, do this:
 
 (note that these instructions are for Windows 2000):
 
 1.  Right click on My Computer and select Manage.  The 
 Computer Management
 window opens.
 2.  Right click on Computer Management and select the 
 Connect to another
 computer...
 3.  Select the computer running the Tomcat service.
 4.  Go to Services and Applications  Services.  Find your 
 service and
 stop it.
 
 Of course, there are Windows permission issues involved, but 
 you presumably
 have the appropriate permissions to do this.
 
 Hope this helps.
 
 Allen
 
  -Original Message-
  From: srinath narasimhan [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, September 24, 2003 4:33 PM
  To: Tomcat Users List
  Subject: RE: Stop Tomcat Remotely
 
 
 
  I tried that, one 8005 is not even open ( I don't know if
  this is because
  tomcat runs as a windows service )
  The documentation says that that can be done only from the
  local computer.
 
  -Original Message-
  From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, September 24, 2003 15:20
  To: Tomcat Users List
  Subject: RE: Stop Tomcat Remotely
 
 
 
  Howdy,
  And what happens if you telnet to the host where tomcat is 
 running, to
  the port specified as the server port (not the connectors) 
 in tomcat's
  server.xml, and type SHUTDOWN?
 
  Yoav Shapira
  Millennium ChemInformatics
 
 
  -Original Message-
  From: srinath narasimhan [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, September 24, 2003 3:14 PM
  To: Tomcat Users List
  Subject: RE: Stop Tomcat Remotely
  
  Well sometimes you have no choice or its not in your hands 
 to decide.
  I know it can be done in unix.
  It can be done in windows as well if you enable telnet or using WMI
  scripts
  ( those involve other security rights issues same as in unix).
  What I was expecting is somehow make a socket ( telnet )
  connection to
  a
  port
  on which the tomcat server is listening ( not 8080 ) and send a
  command.
  
  Thanks.
  
  -Original Message-
  From: Greg Ward [mailto:[EMAIL PROTECTED]
  Sent: Wednesday, September 24, 2003 14:52
  To: Tomcat Users List
  Subject: Re: Stop Tomcat Remotely
  
  
  On 24 September 2003, srinath narasimhan said:
   Is there any way to stop tomcat from remote computer ?
   Tomcat is run as windows service.
  
  Well, how do you normally run commands remotely with Windows?
  If the server is a Unix box, you could do this:
  
ssh [EMAIL PROTECTED] $CATALINA_HOME/bin/catalina.sh stop
  
  or even this:
  
ssh [EMAIL PROTECTED] echo SHUTDOWN | nc localhost 8005
  
  If Windows doesn't have a way to execute commands remotely, what on
  earth are you doing using it as a server OS?
  
  Greg
  
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: 
 [EMAIL PROTECTED]
  
  
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: 
 [EMAIL PROTECTED]
 
 
 
 
  This e-mail, including any attachments, is a confidential business
  communication, and may contain information that is
  confidential, proprietary
  and/or privileged.  This e-mail is intended only for the
  individual(s) to
  whom it is addressed, and may not be saved, copied, printed,
  disclosed or
  used by anyone else.  If you are not the(an) intended
  recipient, please
  immediately delete this e-mail from your computer system and
  notify the
  sender.  Thank you.
 
 
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail

RE: Stop Tomcat Remotely

2003-09-24 Thread Allen Hadden

If it's running as a Windows service, do this:

(note that these instructions are for Windows 2000):

1.  Right click on My Computer and select Manage.  The Computer Management window 
opens.
2.  Right click on Computer Management and select the Connect to another computer...
3.  Select the computer running the Tomcat service.
4.  Go to Services and Applications  Services.  Find your service and stop it.

Of course, there are Windows permission issues involved, but you presumably have the 
appropriate permissions to do this.

Hope this helps.

Allen

 -Original Message-
 From: srinath narasimhan [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, September 24, 2003 4:33 PM
 To: Tomcat Users List
 Subject: RE: Stop Tomcat Remotely
 
 
 
 I tried that, one 8005 is not even open ( I don't know if 
 this is because
 tomcat runs as a windows service )
 The documentation says that that can be done only from the 
 local computer.
 
 -Original Message-
 From: Shapira, Yoav [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, September 24, 2003 15:20
 To: Tomcat Users List
 Subject: RE: Stop Tomcat Remotely
 
 
 
 Howdy,
 And what happens if you telnet to the host where tomcat is running, to
 the port specified as the server port (not the connectors) in tomcat's
 server.xml, and type SHUTDOWN?
 
 Yoav Shapira
 Millennium ChemInformatics
 
 
 -Original Message-
 From: srinath narasimhan [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, September 24, 2003 3:14 PM
 To: Tomcat Users List
 Subject: RE: Stop Tomcat Remotely
 
 Well sometimes you have no choice or its not in your hands to decide.
 I know it can be done in unix.
 It can be done in windows as well if you enable telnet or using WMI
 scripts
 ( those involve other security rights issues same as in unix).
 What I was expecting is somehow make a socket ( telnet ) 
 connection to
 a
 port
 on which the tomcat server is listening ( not 8080 ) and send a
 command.
 
 Thanks.
 
 -Original Message-
 From: Greg Ward [mailto:[EMAIL PROTECTED]
 Sent: Wednesday, September 24, 2003 14:52
 To: Tomcat Users List
 Subject: Re: Stop Tomcat Remotely
 
 
 On 24 September 2003, srinath narasimhan said:
  Is there any way to stop tomcat from remote computer ?
  Tomcat is run as windows service.
 
 Well, how do you normally run commands remotely with Windows?
 If the server is a Unix box, you could do this:
 
   ssh [EMAIL PROTECTED] $CATALINA_HOME/bin/catalina.sh stop
 
 or even this:
 
   ssh [EMAIL PROTECTED] echo SHUTDOWN | nc localhost 8005
 
 If Windows doesn't have a way to execute commands remotely, what on
 earth are you doing using it as a server OS?
 
 Greg
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 This e-mail, including any attachments, is a confidential business
 communication, and may contain information that is 
 confidential, proprietary
 and/or privileged.  This e-mail is intended only for the 
 individual(s) to
 whom it is addressed, and may not be saved, copied, printed, 
 disclosed or
 used by anyone else.  If you are not the(an) intended 
 recipient, please
 immediately delete this e-mail from your computer system and 
 notify the
 sender.  Thank you.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Active Directory Single Sign-On

2003-09-10 Thread Allen Hadden
 -Original Message-
 From: Endre Stølsvik [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, September 10, 2003 3:45 AM
 To: Tomcat Users List
 Subject: Re: Active Directory Single Sign-On
 
 
 | Tim mentioned the use of the JCIFS library.  I don't think 
 that'd work 
 | either since it'd need to run on the same machine as the browser, 
 | which doesn't seem right.  Or perhaps I'm missing 
 something.  Now if 
 | Tomcat supported Windows SSO using JCIFS, then that's a different 
 | story.  I don't think it does though (and I'm sure someone will 
 | correct me if I'm wrong :)).
 
 You're missing something. I'm correcting you! It works. We've 
 done it with our portal engine..!
 

OK, right.  Thanks for the correction.  Very good work, those JCIFS guys.  Sorry for 
the misinformation (and for doubting Tim).

To summarize, there are three ways to do the SSO:

   1. Use IIS to front Tomcat using the ISAPI redirector
   2. Use the JCIFS filter to do the authentication
   3. Use low-level JCIFS calls to implement the authentication yourself

#2 seems like the preferred approach, unless there is a reason you can't tie yourself 
to the   2.3 servlet spec.  It looks like someone recently added an NtlmServlet class 
to JCIFS, which would provide a fourth method to achieve SSO (and wouldn't require a 
2.3 servlet container).

In all cases, there is no password being passed from the browser to the web server.  
Also, you'll have to figure out the best way to do authorization.  You could 
definitely use JNDI to query the ActiveDirectory for authorization information.  But 
does JCIFS provide anything that might help authorization?  For example, does it pass 
a list of groups the user is in as a request attribute?  That'd be nice (a quick look 
at the docs didn't reveal anything).

Allen

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Active Directory Single Sign-On

2003-09-09 Thread Allen Hadden
Probably the easiest way to accomplish this is to use IIS as a front-end to Tomcat 
(using the ISAPI redirector).  In this mode, you'd set up IIS to require 
authentication to the web site.  So by the time the request hits Tomcat, the user is 
already authenticated (IIS does the magic SSO authentication stuff).  I'm pretty sure 
the Tomcat ISAPI redirector passes the user name as a request attribute.  To do this, 
use request.getAttribute(USERNAME).  (The USERNAME value might not be the right 
one...I don't remember off the top of my head).

Now if you need to do authorization (e.g. if you wanted to make sure the user is a 
member of a group), you could use the Windows user name to do an LDAP query to the 
ActiveDirectory.

Also, your original idea about grabbing the user name and password then passing them 
to the server won't work for a couple of reasons.  The primary reason is that there is 
no way in Windows to grab the user's password.

Tim mentioned the use of the JCIFS library.  I don't think that'd work either since 
it'd need to run on the same machine as the browser, which doesn't seem right.  Or 
perhaps I'm missing something.  Now if Tomcat supported Windows SSO using JCIFS, then 
that's a different story.  I don't think it does though (and I'm sure someone will 
correct me if I'm wrong :)).

Good luck!

Allen

 -Original Message-
 From: Pitre, Russell [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, September 09, 2003 4:54 PM
 To: Tomcat Users List
 Subject: RE: Active Directory Single Sign-On
 
 
 Okay, Checked it out, can I use this API to grab the username and
 password with a .jsp or servlet off the NT machine.and 
 then pass it
 to Tomcat so it then can look up users in Active Directory?  
 
 I want security to be container managed.So I need to 
 
 1.)  Grab the username and password 
 2.)  Post it to the login form (action=j_security_check)
 3.)  Tomcat will connect to Active Directory  (JNDI)
 4.)  Tomcat will redirect to the original page called...
 
 
 Does this make sense to everyone?  
 
 
 
 
 -Original Message-
 From: Tim Funk [mailto:[EMAIL PROTECTED] 
 Sent: Tuesday, September 09, 2003 4:17 PM
 To: Tomcat Users List
 Subject: Re: Active Directory Single Sign-On
 
 I think you are looking for NTLM authentication which was done by the
 samba 
 folks. See http://jcifs.samba.org/
 
 -Tim
 
 Pitre, Russell wrote:
 
  Hey All-
  
   
  
  Finally Finally, Finally, I figured out how to authenticate 
 to Active
  Directory...(code below minus the login form).now to go
 further,
  I would like to implement Single Sign-On.somehow we 
 would need to
  retrieve the user's name and password off their NT machine and use
 them
  to automatically post the form..does anyone have any 
 suggestions?
  
   
  
  Also, I was able to see in the log that it enumerates the groups of
 the
  user,  but It didn't find the Domain Users
  group.h.anyone know why?  I see the 
 security group in
 AD
  Comp  Users.. 
  
   
  
  SERVER.XML
  
   
  
  Context
  
  
  
  ..stuff
  
  ..stuff
  
  .stuff 
  
   
  
  Realm className=org.apache.catalina.realm.JNDIRealm
  
  debug=99
  
  connectionURL=ldap://[Domain 
 Controller]:389
  
   
  userBase=OU=Users,OU=Shawmut,DC=[Domain],DC=com
  
  userSearch=(sAMAccountName={0})
  
  userRoleName=member
  
   
  roleBase=OU=Users,OU=Shawmut,DC=[Domain],DC=com
  
  roleName=memberOf
  
   
  roleSearch=(memberOf=CN=tomcat,CN=Users,DC=[Domain],DC=com)
  
   
  connectionName=CN=Administrator,CN=Users,DC=[Domain],DC=com
  
  connectionPassword=[password]
  
  roleSubtree=true
  
  userSubtree=true/
  
  /Context
  
   
  
   
  
  WEB.XML
  
   
  
  security-constraint
  
  display-nameShow Tracker
 Security
  Constraint/display-name
  
  web-resource-collection
  
   
  web-resource-nameProtected Area/web-resource-name
  
   
  url-pattern/*/url-pattern
  
  /web-resource-collection
  
  auth-constraint
  
   
  role-nameCN=Alloffice,OU=SDC,OU=Email Distribution
  Lists,OU=Groups,OU=Shawmut,DC=[Domain],DC=com/role-name
  
  /auth-constraint
  
  /security-constraint
  
   
  
  login-config
  
  auth-methodFORM/auth-method
  
  realm-nameShow Tracker
  Authentication Area/realm-name
  
  form-login-config
  
   
  form-login-page/login.jsp/form-login-page
  
   
  

RE: forward error

2003-09-05 Thread Allen Hadden

It could be in one of your tag libraries, but you probably thought of that already.  :)

I've also seen cases where it's the generated servlet that has out.println calls 
before the redirect.  Perhaps it's the newline character after the %.  Try putting 
all of the directives (page and taglib) on the same line.  For example:

%@ page contentType=...%%@ taglib ... %

You may also want to try looking at the .java file that gets generated to see what's 
going on.

Allen

 -Original Message-
 From: Maxime Colas des Francs [mailto:[EMAIL PROTECTED] 
 Sent: Friday, September 05, 2003 9:39 AM
 To: Tomcat Users List
 Subject: Re: forward error
 
 
 Hi
 
 thks for your response, but here is my code, i don't 
 understand where the 
 response is commited !
 
 _
 
 %@ page contentType=text/html; charset=iso-8859-1 language=java 
 errorPage=/error_jsp.jsp%
 %@ taglib prefix=c uri=http://java.sun.com/jstl/core; %
 %@ taglib prefix=log 
 uri=http://jakarta.apache.org/taglibs/log-1.0; %
 %@ taglib prefix=sql uri=http://java.sun.com/jstl/sql; %
 
 sql:query var=ctcRow
 SELECT DISTINCT email FROM ctc ORDER by email
 /sql:query
 
 c:forEach items=${ctcRow.rows} var=row
 
  log:info category='%= request.getRemoteUser() %'
 c:out value=${row.email}/
  /log:info
 
 /c:forEach
 
 jsp:forward page=/index.jsp/
 
 ___
 
 if i put a autoFlush=false in page directive and a % 
 out.flush(); % 
 just before the forward i have a bufferOverflow ...
 
 
 
 At 16:00 2003-09-04 -0400, you wrote:
 More information ...
 http://jakarta.apache.org/tomcat/faq/misc.html#illegalstate
 -Tim
 
 Shapira, Yoav wrote:
 Howdy,
 Both errors are fairly clear and essentially the same.  You can't
 forward or redirect a response that's been committed, i.e. 
 written to.
 If you're going to forward or redirect a response, you must 
 do so before
 writing to the response.  You can read the JavaDoc for
 HttpServletResponse#sendRedirect and RequestDispatcher#forward.
 Yoav Shapira
 Millennium ChemInformatics
 
 
 -Original Message-
 From: Maxime Colas des Francs [mailto:[EMAIL PROTECTED]
 Sent: Thursday, September 04, 2003 3:37 PM
 To: [EMAIL PROTECTED]
 Subject: forward error
 
 Hi,
 
 - If at the end of on of a jsp file, i put a 
 jsp:forward, i have this
 :
 
 java.lang.IllegalStateException: Error: Attempt to clear a buffer
 that's
 
 already been flushed
  at
 org.apache.jasper.runtime.PageContextImpl.forward(PageConte
 xtImpl.java:
 415)
 
  at 
 org.apache.jsp.test_ps_jsp._jspService(test_ps_jsp.java:448)
  at
 org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:137)
  ...
 
 - if i put a c:redirect, i have this :
 java.lang.IllegalStateException
  at
 org.apache.catalina.connector.HttpResponseFacade.sendRedire
 ct(HttpRespo
 nseF
 
 acade.java:173)
  at
 org.apache.taglibs.standard.tag.common.core.RedirectSupport
 .doEndTag(Re
 dire
 
 ctSupport.java:151)
  at
 org.apache.jsp.test_ps_jsp._jspx_meth_c_redirect_1(test_ps_
 jsp.java:123
 3)
 
  at 
 org.apache.jsp.test_ps_jsp._jspService(test_ps_jsp.java:453)
  ...
 
 - if i put nothing, i have no error ...
 
 sombdy can help me to understand this error ?
 
 
 ---
 --
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: 
 [EMAIL PROTECTED]
 
 
 This e-mail, including any attachments, is a confidential business 
 communication, and may contain information that is confidential, 
 proprietary and/or privileged.  This e-mail is intended 
 only for the 
 individual(s) to whom it is addressed, and may not be 
 saved, copied, 
 printed, disclosed or used by anyone else.  If you are not the(an) 
 intended recipient, please immediately delete this e-mail from your 
 computer system and notify the sender.  Thank you.
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: response.sendRedirect

2003-09-05 Thread Allen Hadden
The one thing you want to watch out for with relative redirects is that they're 
converted by the servlet container to absolute URLs (this is in the servlet spec).  
This is, by the letter of the HTTP spec, the correct thing to do.  Unfortunately, it 
can cause problems in deployments where an proxying SSL accelerator is used.  These 
are proxies that take HTTPS requests and convert them to HTTP requests, handling all 
the SSL crypto stuff in the process (this technique is used in some high-volume 
deployments where SSL is required...the SSL stuff can be done in hardware).

Consider the following:

- browser requests https://visibleserver/a.jsp
- a proxy SSL accelerator does the SSL processing, then forwards the 
  request via standard HTTP to http://realserver/a.jsp
- the web application does some processing, followed by a 
  response.sendRedirect(b.jsp), which the servlet 
  container trainslates to http://realserver/b.jsp.  
  This is probably not what the programmer intended

There are a couple of things you can do to solve this problem:

* Change all sendRedirect calls to use absolute URLs.  This implies that you know the 
absolute URL...it'd have to be a parameter to the web application, or something.

OR

* Implement your own sendRedirect method that sends the relative URL to the browser.  
This does not adhere to the HTTP spec, but all the browsers I tested seem to handle it 
fine (I've read elsewhere that this was the case too).

Anyway, this probably isn't an issue for most people.  If you have a commercial 
application and can't control the deployment, you should at least consider this, 
though.

Allen

 -Original Message-
 From: Christopher Williams [mailto:[EMAIL PROTECTED] 
 Sent: Friday, September 05, 2003 2:22 PM
 To: Tomcat Users List
 Subject: Re: response.sendRedirect
 
 
 Say you're accessing pages on localhost, so your URLs take the form
 http://localhost:8080/war-file/jsp-file
 then the servlet container root is http://localhost:8080/ and 
 a redirect to
 /another-war-file/another.jsp would be a redirect to:
 http://localhost:8080/another-war-file/another.jsp
 
 In sendRedirect, I'm fairly sure that you simply use 
 /cal/form/index.jsp.
 That sort of pattern always works for my webapps.
 
 - Original Message - 
 From: Charlie Toohey [EMAIL PROTECTED]
 To: [EMAIL PROTECTED]
 Sent: Friday, September 05, 2003 7:07 PM
 Subject: response.sendRedirect
 
 
  The Servlet API doc for the sendRedirect method states:
 
  If the location is relative with a leading '/' the container
 interprets
  it as relative to the servlet container root.
 
  I've looked thru the Servlet Spec and can not quite figure 
 out what they
 mean
  by servlet container root ? Is this a typo and supposed to 
 be servlet
 context
  root ? Or is there really such a thing as the servlet 
 container root, and
 if
  so, what is it ?
 
  e.g. if my context path is /cal and I want to redirect to
  /cal/form/index.jsp, what would I use in sendRedirect ?
  (I know I could do a forward, but want to redirect in my situation)
 
  Thanks,
  Charlie
 
 
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: Internationalization Problem

2003-09-04 Thread Allen Hadden

Assuming you're talking about a JSP (and not a static HTML page), try doing this at 
the top of your JSP file:

[EMAIL PROTECTED] contentType=text/html; charset=UTF-8%

Or

response.setContentType(text/html; charset=UTF-8);

(these are equivalent, if memory serves me correctly).

I've always been a little unsure as to how the browsers handle differences in the HTTP 
header and HTTP-EQUIV, but I guess your example shows that it's using the HTTP header 
(the default is ISO-8859-1).  Althought, it might be browser-dependent.  I always just 
make sure they match.

Another thing to look out for...if you're handling posted form data, make sure you 
call request.setCharacterEncoding(UTF-8) before doing the request.getParameter 
calls.  There might be other ways to handle this, depending on your servlet container. 
 I think Tomcat requires the call to request.setCharacterEncoding, but I know that 
iPlanet 6 doesn't support that call.  For iPlanet 6, you have change a configuration 
file to tell it you want posted data to be interpreted as UTF-8.  This is legacy HTTP 
stuff...there's no standard way for a POST to contain the character set of the data 
(the web application just has to know).

Allen

 -Original Message-
 From: Chaitanya Pallapothula [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, September 03, 2003 8:56 PM
 To: [EMAIL PROTECTED]
 Subject: Internationalization Problem
 
 
 Hi 
 I have been working on Internationalization and during
 that process I encountere this strange problem. 
 My server is sending the right characters(Russian) to
 the browser. And also I have put this tag META
 HTTP-EQUIV=Content-Type
 CONTENT=text/html;charset=utf-8 in the head pasrt
 of my out put. 
 
 The problem is browser cannot render the characters
 correctly. And when I see the view - Encoding menu of
 the browser Western Europian(Windows) was selected.
 If I manually change that to UTF-8 it paints the
 correct characters. 
 
 So I added the code(socument.chatset=utf-8) to force
 the browser to select UTF-8 as encoding. This time the
 encoidng was selected as UTF-8 and still the browser
 doesnt paint the characters correctly. If I click on
 view-Encoding-UTF-8 manually(Though utf-8 is
 selected by default). It paints the characters
 correctly. 
 
 I am confused with this kind of behaviour. I am using
 tomcat4.1.12 as my servlet engine and web server. And
 also I am using struts framework(tag lib also). 
 
 Note:  When I set the charset in the response. The
 server doesnt send the right characters to the
 browser. If I dont set any charset in the response
 header, server sends the right charset to the browser.
 
 
  I am also confused whether the problem is browser or
 the server.
 
 Any help would be greatly apreciated. 
 Thanks
 Chaitanya
 
 
 
 
 __
 Do you Yahoo!?
 Yahoo! SiteBuilder - Free, easy-to-use web site design software
 http://sitebuilder.yahoo.com
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



RE: File upload Bug?

2003-09-03 Thread Allen Hadden

I had this (or a similar problem) a long time ago.  It only occurred when connecting 
to IIS via HTTPS (SSL).  Also, my problem was with isapi_redirector.dll, not 
isapi_redirector2.dll.  It might be the same issue, though.

It was some sort of timing problem with the ISAPI redirector.  I hacked around the 
problem in the redirector by reading large POST requests to a temporary file before 
sending them to Tomcat.  This fixed the problem.  At the time, I attributed it to 
some IIS quirk.

Note that what I learned didn't point me to the O'Reilly upload code at all.

If you're interested, I can share the code.  Again, the modifications were to the 
previous version of the redirector.

Allen

 -Original Message-
 From: Tom Lyle [mailto:[EMAIL PROTECTED] 
 Sent: Wednesday, September 03, 2003 11:11 AM
 To: Tomcat Users List
 Subject: RE: File upload Bug?
 
 
 I've just realised something. The machine thats running 
 Tomcat 4.1.27 is
 serving the pages with IIS and isapi_redirector2.dll, when i connect
 directly to Tomcat via port 8080 it works fine.
 
 Right, i've just searched the archives and found 2 people 
 posting (much more
 elequently) the same problem but no solution. Does anyone 
 know how to fix
 this?
 
 thanks
 
 Tom
 
  -Original Message-
  From: Tom Lyle [mailto:[EMAIL PROTECTED]
  Sent: 03 September 2003 15:53
  To: Tomcat Users List
  Subject: File upload Bug?
 
 
  Hi All,
 
  I'm using the o'reilly mutipart request classes to upload 
 files using a
  servlet and its happily working using Tomcat 4.1.18. However,
  i've upgraded
  to the tomcat 4.1.27 and a certain file (just a jpg) causes 
 the upload to
  fail with an java.io.IOException: unexpected end of part. 
 Now i can upload
  this file to the webapp running on Tomcat 4.1.18 but not to the
  same webapp
  running on 4.1.27. What gives?
 
  Running on Windows 2000
  with sun jdk1.4.1
 
  Tom
 
 
  
 -
  To unsubscribe, e-mail: [EMAIL PROTECTED]
  For additional commands, e-mail: [EMAIL PROTECTED]
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]
 
 

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]