Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
F
float
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 16
    • Issues 16
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • ai3
  • float
  • Merge Requests
  • !25

Merged
Opened May 29, 2019 by subvertao@subvertaoDeveloper

Fix proxy

  • Overview 0
  • Commits 6
  • Pipelines 6
  • Changes 1

Ho provato ad aggiustare i valori del proxy di nginx per evitare i seguenti orrori:

May 29 19:30:13 latitanza nginx[26527]: latitanza nginx: 2019/05/29 19:30:13 [crit] 26527#26527: *10914457 cache file "/var/cache/nginx/1/ba/c7f46e900b23d881b7a1b601db8baba1" has too long header, client: ::ffff:185.26.156.96, server: noblogs.org, request: "GET /feed/ HTTP/1.1", host: "antifabochum.noblogs.org"

Quindi mi sono sparato un po' di ricerche e ho trovato questo:

https://www.digitalocean.com/community/tutorials/understanding-nginx-http-proxying-load-balancing-buffering-and-caching

Ma anche questo:

https://github.com/kubernetes/ingress-nginx/issues/363

che in teoria non dovrebbe essere rilevante, ma alla luce dei test sembrerebbe che lo sia, ovvero:

 proxy_buffering on;
 proxy_buffers 4 16k;
 proxy_buffer_size 16k;
 proxy_busy_buffers_size 16k;

il 16k in proxy_buffers deve essere uguale a quello in proxy_buffer_size, altrimenti il job fallisce. Siccome questo e' un approccio alquanto approssimativo faccio una pull request :-)

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Reference: ai3/float!25
Source branch: fix-proxy

Revert this merge request

This will create a new commit in order to revert the existing changes.

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.

Cherry-pick this merge request

Switch branch
Cancel
A new branch will be created in your fork and a new merge request will be started.