Skip to content
This repository has been archived by the owner on Apr 4, 2024. It is now read-only.

Running bors locally and cannot access over https #1495

Open
acepaceNS opened this issue Apr 24, 2022 · 0 comments
Open

Running bors locally and cannot access over https #1495

acepaceNS opened this issue Apr 24, 2022 · 0 comments

Comments

@acepaceNS
Copy link

I'm using latest bors-ng and building my own container.

Running it, bors finishes the initialization properly

16:15:07.356 pid=<0.2099.0> [warning] Phoenix.Endpoint.CowboyAdapter is deprecated and it will be removed in next versions. Please make sure {:plug_cowboy, "~> 2.1"} or later is listed in your mix.exs
16:15:07.362 pid=<0.2066.0> [info] Access BorsNG.Endpoint at https://myserver.com

But when I attempt to access it using wget, I get the following failure

16:15:16.637 pid=<0.2305.0> [error] Cowboy returned 400 because it was unable to parse the request headers.

This may happen because there are no headers, or there are too many headers
or the header name or value are too large (such as a large cookie).

You can customize those values when configuring your http/https
server. The configuration option and default values are shown below:

    protocol_options: [
      max_header_name_length: 64,
      max_header_value_length: 4096,
      max_headers: 100,
      max_request_line_length: 8096
    ]

Unclear where I have gone wrong with the dev instructions

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant