-
Notifications
You must be signed in to change notification settings - Fork 27
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
Allow default Java user agent #20
Comments
This is unfortunately a limitation of Cloudflare. It seems there is no way from Dashboard to whitelist a specific user agent I am reaching out them to seek for a solution. If this cannot be workarounded, then will add SO hacks to homepage as a reference to other developers. |
This unfortunately cannot be easily workarounded with cloudflare. I am trying to switch to AWS cloudfront. |
Unfortunately AWS cloudfront is not an option because they don't provide SSL solution. I have linked SO from homepage though. |
In fact, Cloudflare guys helped solving the issue.
|
I'm using maven to generate javadocs and I'm running into the same issue. This is my maven javadoc plugin config:
I get this error when I run the javadoc generation with maven in debug mode:
|
I have narrowed it down to the the
But hitting a URL like So the solution would be to configure the server serving |
As indicated here, the javadoc tool must be told to change its User Agent, for the default one seems to be forbidden access to javadoc.io. And as indicated in a comment, the workaround of changing the default user agent for the javadoc tool doesn’t seem to work any more (that part is obviously not your fault).
Please consider hosting the service with a provider that does not exclude default Java user agent, for simpler (or even for possible!) access to the service.
(Not sure if this issue relates to #17, I suppose not, as that one is closed.)
The text was updated successfully, but these errors were encountered: