etherpad-lite/tests/ratelimit/Dockerfile.anotherip

FROM node:alpine3.12
WORKDIR /tmp
RUN npm i etherpad-cli-client@0.0.9
COPY ./tests/ratelimit/send_changesets.js /tmp/send_changesets.js
security: Support proxy with rate limiting and include CI test coverage for nginx rev proxy (#4373) Previously Etherpad would not pass the correct client IP address through and this caused the rate limiter to limit users behind reverse proxies. This change allows Etherpad to use a client IP passed from a reverse proxy. Note to devs: This header can be spoofed and spoofing the header could be used in an attack. To mitigate additional steps should be taken by Etherpad site admins IE doing rate limiting at proxy. This only really applies to large scale deployments but it's worth noting. 2020-10-01 11:39:01 +02:00			`FROM node:alpine3.12`
			`WORKDIR /tmp`
does that help? 2020-11-08 18:51:52 +01:00			`RUN npm i etherpad-cli-client@0.0.9`
security: Support proxy with rate limiting and include CI test coverage for nginx rev proxy (#4373) Previously Etherpad would not pass the correct client IP address through and this caused the rate limiter to limit users behind reverse proxies. This change allows Etherpad to use a client IP passed from a reverse proxy. Note to devs: This header can be spoofed and spoofing the header could be used in an attack. To mitigate additional steps should be taken by Etherpad site admins IE doing rate limiting at proxy. This only really applies to large scale deployments but it's worth noting. 2020-10-01 11:39:01 +02:00			`COPY ./tests/ratelimit/send_changesets.js /tmp/send_changesets.js`