Status update:
It turned out that openid auth exception wasn't properly handled on l-l-p side. This was fixed by https://code.launchpad.net/~pfalcon/linaro-license-protection/openid-exception-for-internal-hosts/+merge/149807 (with testcase) and then deployed. Unfortunately, that didn't fixed the issue described in this bug. (As a quicker testcase, following url may be used: https://android-build.linaro.org/api/proxy-remote-file?url=https://snapshots.linaro.org/android/~linaro-android-restricted/juice-aosp/103/lava-job-info ; expected outcome is JSON data).
Danilo was looking at this shortly, and it seems that issue is on Apache side after all, even though it contains directives for lava-job-info file now.
Status update:
It turned out that openid auth exception wasn't properly handled on l-l-p side. This was fixed by https:/ /code.launchpad .net/~pfalcon/ linaro- license- protection/ openid- exception- for-internal- hosts/+ merge/149807 (with testcase) and then deployed. Unfortunately, that didn't fixed the issue described in this bug. (As a quicker testcase, following url may be used: https:/ /android- build.linaro. org/api/ proxy-remote- file?url= https:/ /snapshots. linaro. org/android/ ~linaro- android- restricted/ juice-aosp/ 103/lava- job-info ; expected outcome is JSON data).
Danilo was looking at this shortly, and it seems that issue is on Apache side after all, even though it contains directives for lava-job-info file now.