On 18 December 2014 at 14:06, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Duncan,
>
> On 12/18/14 4:18 AM, Lyallex wrote:
>> On 17 December 2014 at 22:37, Christopher Schultz
>> wrote: Duncan,
>>
>> On 12/17/14 12:32 PM, Lyallex wrote:
> Yea I thought of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Duncan,
On 12/18/14 4:18 AM, Lyallex wrote:
> On 17 December 2014 at 22:37, Christopher Schultz
> wrote: Duncan,
>
> On 12/17/14 12:32 PM, Lyallex wrote:
Yea I thought of this, the problem is I currently have a user
area that requires a
On 17 December 2014 at 22:37, Christopher Schultz
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA256
>
> Duncan,
>
> On 12/17/14 12:32 PM, Lyallex wrote:
>> Yea I thought of this, the problem is I currently have a user area
>> that requires a login and all this is currently configured in
>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Duncan,
On 12/17/14 12:32 PM, Lyallex wrote:
> Yea I thought of this, the problem is I currently have a user area
> that requires a login and all this is currently configured in
> web.xml and I'm not sure how all this will fit together. I'll try a
Yea I thought of this, the problem is I currently have a user area
that requires a login and all this is currently configured in web.xml
and I'm not sure how all this will fit together. I'll try a few things
out and see what happens.
Thanks for taking the time to respond
Duncan
On 17 December 20
On 17/12/2014 17:10, Lyallex wrote:
> Tomcat 7.0.42
> jdk1.7.0_51
> Ubuntu 12.04/CentOS dev/deploy
>
> I have been reading more and more about Google and the like
> prioritising sites that employ https/ssl by default. Currently my site
> does not use https but delegates payment to a secure payment
Tomcat 7.0.42
jdk1.7.0_51
Ubuntu 12.04/CentOS dev/deploy
I have been reading more and more about Google and the like
prioritising sites that employ https/ssl by default. Currently my site
does not use https but delegates payment to a secure payment provider
who does, thusly I have avoided going th
