maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Boué (JIRA) <j...@apache.org>
Subject [jira] [Comment Edited] (MJAVADOC-533) <link> entries that point to a resource that requires an Accept header may be ignored
Date Thu, 09 Aug 2018 18:33:00 GMT

    [ https://issues.apache.org/jira/browse/MJAVADOC-533?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16575254#comment-16575254
] 

Guillaume Boué edited comment on MJAVADOC-533 at 8/9/18 6:32 PM:
-----------------------------------------------------------------

We could add a Accept header of {{\*/\*}} (I thought was the default according to the HTTP
spec (https://tools.ietf.org/html/rfc7231#section-5.3.2)). I was able to reproduce the 403
response code generating the docs for {{https://docs.spring.io/spring/docs/5.0.3.RELEASE/javadoc-api/}},
and adding the header seemed to fix it.


was (Author: gboue):
We could add a Accept header of {{*/*}} (I thought was the default according to the HTTP spec
(https://tools.ietf.org/html/rfc7231#section-5.3.2)). I was able to reproduce the 403 response
code generating the docs for {{https://docs.spring.io/spring/docs/5.0.3.RELEASE/javadoc-api/}},
and adding the header seemed to fix it.

> <link> entries that point to a resource that requires an Accept header may be ignored
> -------------------------------------------------------------------------------------
>
>                 Key: MJAVADOC-533
>                 URL: https://issues.apache.org/jira/browse/MJAVADOC-533
>             Project: Maven Javadoc Plugin
>          Issue Type: Bug
>    Affects Versions: 3.0.1
>            Reporter: Andy Wilkinson
>            Priority: Minor
>
> This is a regression caused by the changes made to fix MJAVADOC-427.
> The HTTP client configuration that's used to get the redirect URLs does not include an
{{Accept}} header in the requests that it makes. This can result in a 403 response for some
javadoc, such as Spring Framework's which is fronted by Cloudflare. The lack of {{Accept}}
header will sometimes cause Cloudflare to respond with a 403 containing a Captcha.
> I'm a member of the Spring Framework team and have asked our sysadmin to look at tweaking
Cloudflare's rules, but I thought it worth reporting the problem here as others may be affected
and may not be in a position to change the server's configuration.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message