|
Should also mention .. the OPTIONS request comes in *without* a user, hence the 401 .. ==== I’ve got a tomcat app with apache (2.2) in front of
it. Apache handles the auth through LDAP and requires membership in a specific
group. One of the app features allows the user to generate an csv file from
some data and download it. When this download fires with an IE client, the
browser also issues an HTTP OPTIONS request against / which fails with a 401
and pops the auth dialog again. Users can just cancel that dialog and proceed,
but I’d rather it didn’t appear at all! Is there some way to
configure apache to route OPTIONS requests to the bit-bucket? Is it Apache or
really Tomcat that’s generating the 401? Any hints/clues appreciated! jd
The information contained in this communication is confidential and may contain information that is privileged or exempt from disclosure under applicable law. If you are not a named addressee, please notify the sender immediately and delete this email from your system. If you have received this communication, and are not a named recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. |
|