poodle | A Proof of Concept for the POODLE vulnerability in SSLv3 | Hacking library

I figured it out: it turns out the Nginx server was missing it's MIME types (the browser thought that the css file was text/plain instead of text/css).

Usually the best practice is to add files to /etc/nginx/conf.d/ (and mount your docker volume there) instead of editting nginx.conf directly, but I wanted to be able to place other files in the /etc/nginx/ directory so I decided to mount my docker volume there.

As it turns out, that's a bad idea. I overwrote a lot of other important config files inside the docker container. Now, I could just copy all of those files into my docker volume and call it good, but I decided it would be worth doing it the "right" way so I don't mess up stuff in the future.

So, now I have a docker volume mounted at /etc/nginx/cond.f/ and another volume mounted at /etc/nginx/lib/ so that I can import files without the main nginx.conf reading is as a server config.

The problem is that when you use position: fixed;, the element is no longer relative to the container but relative to the page or in other words positioned absolute. That makes it appear on top of the 2nd div. The solution is that you can use position: sticky; instead.. The appearance is a bit different though...

Try hitting the compete url of your EC2 instance

You could include the range as another condition in your .loc selection (for the general case, I'll explicitly include the 0):

Ok. I created an error_404.html:

sudo vim /usr/share/nginx/html/error_404.html

with:

In Prolog, an n-ary predicate p, for n≥0, is defined by a procedure, which consists of one or more clauses whose conclusions are terms of the form p(a1, ..., an), where each a_i is an argument. Clauses belonging to the same procedure are expected to be declared in sequence, contiguously.

When the clauses of two or more distinct procedures appear interleaved in the source code, the compiler produces the warning messages you get. To suppress such messages, you can use a directive of the form :- discontiguous predicate/arity.

For example:

I found the issue. On a hunch, I investigated the whitespace.

Bingo got it working. Thanks to @razvans and @engineersmnky for pointing me in the right direction.

Yes I had references to passenger_ruby but it was in the wrong place. I had to go to /etc/nginx/sites-available and add passenger_ruby /path/to/ruby

To find out what the /path/to/ruby is use passenger-config about ruby-command and use the value at Command.

This code appears to work: