Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

--rrdp-keep-responses does not keep responses for repository that uses redirects #935

Open
ties opened this issue Feb 7, 2024 · 1 comment

Comments

@ties
Copy link
Contributor

ties commented Feb 7, 2024

As a user, when I use routinator --rrdp-keep-responses ~/src/tmp/routinator-responses -vv server to log RRDP responses, I see an empty file for the repository at https://rpki1.rpki-test.sit.fraunhofer.de/rrdp/notification.xml.

I think that this is the only repository using redirects.
This may be the only repository redirecting to a different FQDN.

$ routinator --rrdp-keep-responses ~/src/tmp/routinator-responses -vvv server
...
[DEBUG] starting new connection: https://rpki1.rpki-test.sit.fraunhofer.de/
[DEBUG] redirecting 'https://rpki1.rpki-test.sit.fraunhofer.de/rrdp/notification.xml' to 'https://c514fb3d-739f-478e-8c0e-1f14f751fee1.rpki.rpki-test.sit.fraunhofer.de/rrdp/notification.xml'
[DEBUG] starting new connection: https://c514fb3d-739f-478e-8c0e-1f14f751fee1.rpki.rpki-test.sit.fraunhofer.de/
~/src/tmp/routinator-responses/rpki1.rpki-test.sit.fraunhofer.de/rrdp/notification.xml$ ls -al
total 0
drwxr-xr-x@ 4 me  staff  128 Feb  7 15:45 .
drwxr-xr-x@ 3 me  staff   96 Feb  7 15:38 ..
-rw-r--r--@ 1 me  staff    0 Feb  7 15:38 2024-02-07T14:38:21.221806+00:00
-rw-r--r--@ 1 me  staff    0 Feb  7 15:45 2024-02-07T14:45:44.994853+00:00
@ties
Copy link
Contributor Author

ties commented Feb 7, 2024

This repository seems to be using dynamic hostnames. This can cause metric (or well, when storing files, directory) bloat.

PNG image

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

No branches or pull requests

1 participant