thank you for your answers and short clarification. see my answers and further
questions inline.
>In short:
>1. Cookies are usually sent by a single multi-valued "Cookie" header.
>If the header has incorrect value, then the client is sending an
>incorrect request which has to be rejected as inval
On Apr 13, 2013 3:55 PM, "Mark Eggers" wrote:
>
> On 4/10/2013 5:47 PM, Howard W. Smith, Jr. wrote:
>>
>> Some legit 404s definitely show up for every enduser that access the
webapp
>> via mobile device, because PrimeFaces has 2 files that no longer exist in
>> the JAR file, and I just reported th
On 4/10/2013 5:47 PM, Howard W. Smith, Jr. wrote:
Some legit 404s definitely show up for every enduser that access the webapp
via mobile device, because PrimeFaces has 2 files that no longer exist in
the JAR file, and I just reported this in their Issue Tracker.
127.0.0.1 - - [10/Apr/2013:20:00:
2013/4/13 Keszthelyi Laszlo :
> Hi,
>
> we are facing problems with cookies containing umplaut (or other special
> characters), causing the request processing beeing stopped and returning a
> blank page.
> I know that umlaut characters are forbidden within cookies, except when they
> are urlenco
Hi,
we are facing problems with cookies containing umplaut (or other special
characters), causing the request processing beeing stopped and returning a
blank page.
I know that umlaut characters are forbidden within cookies, except when they
are urlencoded, but the problem arises from third-part
On 13 Apr 2013, at 03:33, Esmond Pitt wrote:
> I agree with your comment. Adding a second box for Tomcat only means I also
> have to configure a firewall between them, whereas using 127.0.0.x for
> Tomcat protects it completely.
No it doesn't!
Obfuscation or indirection != security.
HTTPD doesn
