-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Pid,
On 7/1/2010 3:31 AM, Pid wrote:
> On 01/07/2010 02:30, Christopher Schultz wrote:
>> Matthew,
>>
>> On 6/30/2010 8:20 PM, Matthew Mauriello wrote:
>>> The behavior seems rather strange to me in fact, I've seen other websites
>>> run on what looks
Christopher,
Great news (for me), seems the problem was that because I was using
relative linking and sending the credentials to log the user in to SOLR
the links on the landing page were being recreated with the same
credentials in them so I just put in direct link locations in and and for
the mo
On 01/07/2010 02:30, Christopher Schultz wrote:
> Matthew,
>
> On 6/30/2010 8:20 PM, Matthew Mauriello wrote:
>> The behavior seems rather strange to me in fact, I've seen other websites
>> run on what looks to be BASIC Authentication without popping these browser
>> messages when leaving secured
> From: Matthew Mauriello [mailto:mm578...@albany.edu]
> Subject: Re: Question about BASIC Authentication
>
> how do websites grant access to public sites and secure
> certain sections?
By using the servlet-spec defined mechanisms with a for
the protected areas.
> Or
Christopher,
I may have found a problem in the SOLR header.jsp file that I am using in
navigation. The header.jsp file might be trying to send headers,
unfortunately I am not in the same location as the server so I will have
to check this out tomorrow.
I'll keep you posted,
~Matt
> -BEGIN P
Christopher,
First off, I really appreciate your responses.
Unfortunately I do not have a link that I can send out.
I generally use Mozilla Firefox, Microsoft recently implemented a patch
that prevents http://user:passw...@website.com/SOLR/ from working.
So on this consistent implementation met
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew,
On 6/30/2010 8:20 PM, Matthew Mauriello wrote:
> The behavior seems rather strange to me in fact, I've seen other websites
> run on what looks to be BASIC Authentication without popping these browser
> messages when leaving secured sections.
Christopher,
The behavior seems rather strange to me in fact, I've seen other websites
run on what looks to be BASIC Authentication without popping these browser
messages when leaving secured sections.
See the http://user:passw...@website.com/SOLR is only used once and it
might actually be http:/
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matthew,
On 6/30/2010 12:07 AM, Matthew Mauriello wrote:
> I have two directories in 'webapps' other than ROOT. ROOT redirects users
> to webappA. WebappA does not use tomcat's basic authentication but if you
> log into the application there are links
Christopher,
Thanks for the response.
I have two directories in 'webapps' other than ROOT. ROOT redirects users
to webappA. WebappA does not use tomcat's basic authentication but if you
log into the application there are links inside it that sends the user to
the SOLR webapp via http://user:passw
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Matt,
On 6/29/2010 5:57 PM, Matthew Mauriello wrote:
> I am having a minor problem related to Tomcat's BASIC Authentication setup.
>
> A user access my custom web application in the 'webapps' folder which is
> accessible to everyone in a separate sub
Hello,
I am having a minor problem related to Tomcat's BASIC Authentication setup.
A user access my custom web application in the 'webapps' folder which is
accessible to everyone in a separate sub folder. I have another 'webapps'
sub folder for SOLR which is secured with BASIC Authentication. I h
12 matches
Mail list logo
