You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@jspwiki.apache.org by Derek Hohls <dh...@csir.co.za> on 2016/01/04 07:27:15 UTC

Re: A way to find dead links for external pages

There seem to be any number of tools out there... have you seen:
https://wummel.github.io/linkchecker/
(showing my bias towards Python)



>>> Foster Schucker <Fo...@Schucker.org> 12/28/15 8:39 PM >>>
Thanks.  I didn't think there was a way in JSPWiki to do that.  I was on 
the look for a tool that was smart enough to do the walk and only report 
back on external sites/links.   I figured with the number of people on 
this list that do that I could get a quick recommendation of a tool that 
someone liked.

Thanks!

Foster
On Mon, 28 Dec 2015 19:09:43 +0100, Harry Metske 
<ha...@gmail.com> wrote:

    There has been a discussion about this before:
    https://issues.apache.org/jira/browse/JSPWIKI-330

    We considered it a security risk and did not implement it.

    kind regards,
    Harry


    On 28 December 2015 at 16:14, Foster Schucker <Fo...@schucker.org>
    wrote:

     > I have a wiki that ties into external sites. As these places
    switch to
     > new platforms the old links die. (Or they die due to refactoring).
     >
     > Anyway I'm looking for a way to walk the wiki pages and see if
    there is a
     > 200 response back from the other side. I'm guessing one of you
    have had to
     > do this before, no sense in reinventing the wheel.
     >
     > In a perfect world it would spit out [PageName] URL ResponseCode
    for each
     > URL (that would let me catch other errors like forbidden, etc.
    but I'd be
     > happy to get the ones that don't produce a 200.
     >
     > Thanks!
     > Foster
     >
     >



-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.

Please consider the environment before printing this email.




-- 
This message is subject to the CSIR's copyright terms and conditions, e-mail legal notice, and implemented Open Document Format (ODF) standard. 
The full disclaimer details can be found at http://www.csir.co.za/disclaimer.html.

This message has been scanned for viruses and dangerous content by MailScanner, 
and is believed to be clean.

Please consider the environment before printing this email.

Re: A way to find dead links for external pages

Posted by Paul Uszak <pa...@gmail.com>.
What security issues does this present?

Remember, the link targets have been selected by the wiki authors so they
are desirable links rather than spam.  I can't quite see a threat model if
all you're doing is reporting a HTTP status code.  Isn't this what search
engines do by default?

On 4 January 2016 at 06:27, Derek Hohls <dh...@csir.co.za> wrote:

> There seem to be any number of tools out there... have you seen:
> https://wummel.github.io/linkchecker/
> (showing my bias towards Python)
>
> >>> Foster Schucker <Fo...@Schucker.org> 12/28/15 8:39 PM >>>
> Thanks. I didn't think there was a way in JSPWiki to do that. I was on
> the look for a tool that was smart enough to do the walk and only report
> back on external sites/links. I figured with the number of people on
> this list that do that I could get a quick recommendation of a tool that
> someone liked.
>
> Thanks!
>
> Foster
> On Mon, 28 Dec 2015 19:09:43 +0100, Harry Metske
> <ha...@gmail.com> wrote:
>
> There has been a discussion about this before:
> https://issues.apache.org/jira/browse/JSPWIKI-330
>
> We considered it a security risk and did not implement it.
>
> kind regards,
> Harry
>
>
> On 28 December 2015 at 16:14, Foster Schucker <Fo...@schucker.org>
> wrote:
>
> > I have a wiki that ties into external sites. As these places
> switch to
> > new platforms the old links die. (Or they die due to refactoring).
> >
> > Anyway I'm looking for a way to walk the wiki pages and see if
> there is a
> > 200 response back from the other side. I'm guessing one of you
> have had to
> > do this before, no sense in reinventing the wheel.
> >
> > In a perfect world it would spit out [PageName] URL ResponseCode
> for each
> > URL (that would let me catch other errors like forbidden, etc.
> but I'd be
> > happy to get the ones that don't produce a 200.
> >
> > Thanks!
> > Foster
> >
> >
>
>
>
> --
> This message is subject to the CSIR's copyright terms and conditions,
> e-mail legal notice, and implemented Open Document Format (ODF) standard.
> The full disclaimer details can be found at
> http://www.csir.co.za/disclaimer.html.
>
> This message has been scanned for viruses and dangerous content by
> MailScanner,
> and is believed to be clean.
>
> Please consider the environment before printing this email.
>
>
> --
> This message is subject to the CSIR's copyright terms and conditions,
> e-mail legal notice, and implemented Open Document Format (ODF) standard.
> The full disclaimer details can be found at
> http://www.csir.co.za/disclaimer.html.
>
>
> This message has been scanned for viruses and dangerous content by
> *MailScanner* <http://www.mailscanner.info/>,
> and is believed to be clean.
>
>
> Please consider the environment before printing this email.
>
>