You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@sling.apache.org by Yogesh Upadhyay <up...@gmail.com> on 2015/01/08 02:20:24 UTC
Re: broken documentation URLs returned by google
Yes. I saw that today as well. Most of the link are referred from original sling doc.
Yogesh
On Jan 7, 2015, at 4:15 PM, Henry Saginor <hs...@gmail.com> wrote:
> I am not sure if anyone else has reported this. But some sling documentation URLs return 500 errors. See some examples bellow.
>
> http://sling.apache.org/site/maven-archetypes.html
> http://sling.apache.org/site/output-rewriting-pipelines-orgapacheslingrewriter.html
> http://sling.apache.org/site/rewriting-the-output-through-pipelines.html
>
> These are all returned by google. This http://sling.apache.org/documentation/bundles/output-rewriting-pipelines-org-apache-sling-rewriter.html works fine for example.
> But if you goole any common sling term like “sling rewriter” you might get broken URLs.
Re: broken documentation URLs returned by google
Posted by Daniel Klco <da...@gmail.com>.
The change I made seemed to fix the error in sling.staging.apache.org, but
it was inconsistent on the production website. It seems to be working now,
but it's probably worth following up with infrastructure to ensure there's
not some other issue.
Regards,
Dan
On Thu, Jan 8, 2015 at 5:59 AM, Carsten Ziegeler <cz...@apache.org>
wrote:
> Am 08.01.15 um 11:48 schrieb Bertrand Delacretaz:
> > On Thursday, January 8, 2015, Bertrand Delacretaz <
> bdelacretaz@apache.org>
> > wrote:
> >
> >> ...I have created https://issues.apache.org/jira/browse/INFRA-8995 ...
> >>
> >
> > Turns out this was a syntax error in site/.htaccess - fixed by Dan in
> > revision 1650202, thanks!
> >
> Interesting, I've updated the site after that (at least I thought so)
> and that didn't update the .htaccess file
> Or I did something totally wrong...
>
> Anyways, I also sorted the entries in the .htaccess file
>
> Carsten
> --
> Carsten Ziegeler
> Adobe Research Switzerland
> cziegeler@apache.org
>
Re: broken documentation URLs returned by google
Posted by Carsten Ziegeler <cz...@apache.org>.
Am 08.01.15 um 11:48 schrieb Bertrand Delacretaz:
> On Thursday, January 8, 2015, Bertrand Delacretaz <bd...@apache.org>
> wrote:
>
>> ...I have created https://issues.apache.org/jira/browse/INFRA-8995 ...
>>
>
> Turns out this was a syntax error in site/.htaccess - fixed by Dan in
> revision 1650202, thanks!
>
Interesting, I've updated the site after that (at least I thought so)
and that didn't update the .htaccess file
Or I did something totally wrong...
Anyways, I also sorted the entries in the .htaccess file
Carsten
--
Carsten Ziegeler
Adobe Research Switzerland
cziegeler@apache.org
broken documentation URLs returned by google
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Thursday, January 8, 2015, Bertrand Delacretaz <bd...@apache.org>
wrote:
> ...I have created https://issues.apache.org/jira/browse/INFRA-8995 ...
>
Turns out this was a syntax error in site/.htaccess - fixed by Dan in
revision 1650202, thanks!
-Bertrand
>
Re: broken documentation URLs returned by google
Posted by Bertrand Delacretaz <bd...@apache.org>.
On Thursday, January 8, 2015, Felix Meschberger <fm...@adobe.com> wrote:
> ...this seems to gave been a temporary issue. At first, I could
reproduce, but now
> I get all these pages back …
Testing with curl to avoid caching effects I see about 30% of the requests
failing. I have created https://issues.apache.org/jira/browse/INFRA-8995
-Bertrand
Re: broken documentation URLs returned by google
Posted by Felix Meschberger <fm...@adobe.com>.
Hi
Strange, this seems to gave been a temporary issue. At first, I could reproduce, but now I get all these pages back …
Regards
Felix
> Am 08.01.2015 um 02:20 schrieb Yogesh Upadhyay <up...@gmail.com>:
>
> Yes. I saw that today as well. Most of the link are referred from original sling doc.
>
> Yogesh
> On Jan 7, 2015, at 4:15 PM, Henry Saginor <hs...@gmail.com> wrote:
>
>> I am not sure if anyone else has reported this. But some sling documentation URLs return 500 errors. See some examples bellow.
>>
>> http://sling.apache.org/site/maven-archetypes.html
>> http://sling.apache.org/site/output-rewriting-pipelines-orgapacheslingrewriter.html
>> http://sling.apache.org/site/rewriting-the-output-through-pipelines.html
>>
>> These are all returned by google. This http://sling.apache.org/documentation/bundles/output-rewriting-pipelines-org-apache-sling-rewriter.html works fine for example.
>> But if you goole any common sling term like “sling rewriter” you might get broken URLs.
>