Reposilite is not pulling WSDL files from my upstream repository.

[eaidan1]

What happened?

We deploy WSDL files to Maven and consume them in client projects.

The coordinates for my artifact look like this in the Maven error output: com.example:my-library:wsdl:authService:12.0.0.0

I understand that I can restrict downloading by file type. This Reposilite repository mirrors 4 upstream repositories (self-hosted in Nexus). They are all configured with no allowed extensions, which according to the UI means that all extensions should be permitted.

Maybe it doesn't like the mixed case in the classifier? I don't know why it should care though.

There are no errors reported in Reposilite, it just doesn't serve the file. I looked on the Reposilite server and confirmed that the file is not in the Reposilite repository.

Reposilite version

3.x

Relevant log output

[eaidan1]

I apologize ... there are errors in the logs saying it can't request the file from the upstream reason: illegal EXTENSION. However as I said, I don't have any extensions configured and the UI says that means it shouldn't block downloading due to extensions.

I downloaded the JSON configuration and looked for extensions just in case there is extension info not showing in the UI but there is nothing. It seems like the UI is misrepresenting its behaviour. It says List of accepted file extensions. If none are given, all files can be obtained from this mirror.. But actually the behaviour seems to be that if none are given, it uses some predefined list of extensions.

We can work around this but for us it is not optimal.

[eaidan1]

I hit ctrl-F5 in the UI and now I see that my mirrored repositories do list extensions. I double-checked this because I was sure I had seen that adding a repository preconfigures the list of allowed extensions but when I went back to review it didn't show them. But now they are showing and the behaviour makes sense. Since I can't attest with complete certainty that this is not user error I am going to close this.

[eaidan1]

Actually, I had downloaded the configuration as JSON before and indeed it didn't list the extensions and was also missing some other properties like allowedGroups, httpProxy, authenticatedFetchingOnly, preserveSnapshots, and several others. I downloaded the configuration now and they are there. Something really is broken here.

[dzikoysk]

So I just checked and it seems to be working when allowedExtensions list is actually empty:

{
        "id": "jitpack",
        "visibility": "HIDDEN",
        "redeployment": false,
        "preserveSnapshots": false,
        "storageProvider": {
          "type": "fs",
          "quota": "100%",
          "mount": "",
          "maxResourceLockLifetimeInSeconds": 60
        },
        "storagePolicy": "PRIORITIZE_UPSTREAM_METADATA",
        "metadataMaxAge": 0,
        "proxied": [
          {
            "reference": "https://jitpack.io",
            "store": true,
            "allowedGroups": [],
            "allowedExtensions": [],
            "connectTimeout": 3,
            "readTimeout": 15,
            "httpProxy": "",
            "authenticatedFetchingOnly": false
          }
        ]
      }

I've noticed that if you'll keep it like that:

then the configuration will look like this:

"allowedExtensions": [
    ""
],

and it'll be indeed broken 😬 The UI for the configuration is quite terrible hah, I'll filter out these empty values.

[dzikoysk]

Can you check if that was the actual problem or not? Also make sure to hit this Update and reload button, sadly we don't have auto-save 😔

[eaidan1]

I was clicking Update and Reload.

I don't think that was the issue because later when I went in to the UI the default list of extensions was there. I didn't add them.

Also numerous keys were just completely missing from the JSON. In the following image left is the configuration I downloaded while it was broken, right is the configuration from the next day. You can see I did add .wsdl after it loaded properly. I did not add the others though.

73a74,75
>         "metadataMaxAge": 0,
>         "preserveSnapshots": false,
75a78,80
>             "allowedExtensions": [],
>             "allowedGroups": [],
>             "authenticatedFetchingOnly": false,
80a86,88
>             "connectTimeout": 3,
>             "httpProxy": "",
>             "readTimeout": 15,
84a93,107
>             "allowedExtensions": [
>               ".jar",
>               ".war",
>               ".pom",
>               ".xml",
>               ".module",
>               ".md5",
>               ".sha1",
>               ".sha256",
>               ".sha512",
>               ".asc",
>               ".wsdl"
>             ],
>             "allowedGroups": [],
>             "authenticatedFetchingOnly": false,
89a113,115
>             "connectTimeout": 3,
>             "httpProxy": "",
>             "readTimeout": 15,
93a120,133
>             "allowedExtensions": [
>               ".jar",
>               ".war",
>               ".pom",
>               ".xml",
>               ".module",
>               ".md5",
>               ".sha1",
>               ".sha256",
>               ".sha512",
>               ".asc"
>             ],
>             "allowedGroups": [],
>             "authenticatedFetchingOnly": false,
98a139,141
>             "connectTimeout": 3,
>             "httpProxy": "",
>             "readTimeout": 15,
102a146,159
>             "allowedExtensions": [
>               ".jar",
>               ".war",
>               ".pom",
>               ".xml",
>               ".module",
>               ".md5",
>               ".sha1",
>               ".sha256",
>               ".sha512",
>               ".asc"
>             ],
>             "allowedGroups": [],
>             "authenticatedFetchingOnly": false,
107a165,167
>             "connectTimeout": 3,
>             "httpProxy": "",
>             "readTimeout": 15,
111a172
>         "redeployment": false,
114c175,178
<           "quota": "100%"
---
>           "maxResourceLockLifetimeInSeconds": 60,
>           "mount": "",
>           "quota": "100%",
>           "type": "fs"
119a184,185
>         "metadataMaxAge": 0,
>         "preserveSnapshots": false,
121a188,201
>             "allowedExtensions": [
>               ".jar",
>               ".war",
>               ".pom",
>               ".xml",
>               ".module",
>               ".md5",
>               ".sha1",
>               ".sha256",
>               ".sha512",
>               ".asc"
>             ],
>             "allowedGroups": [],
>             "authenticatedFetchingOnly": false,
126a207,209
>             "connectTimeout": 3,
>             "httpProxy": "",
>             "readTimeout": 15,
134c217,220
<           "quota": "100%"
---
>           "maxResourceLockLifetimeInSeconds": 60,
>           "mount": "",
>           "quota": "100%",
>           "type": "fs"

One thing that did occur to me is that maybe the password (for the upstream) is messing it up. The password has a lot of extended ASCII characters in it. When I try to open the configuration file in Oxygen it says the following.

Cannot open the specified file: Got a character encoding exception.
 File encoding (UTF8) does not support all characters from the current file.

This is conjecture and might just be an Oxygen problem, it is just something I noticed. It is currently working with the same password.