You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by David Jencks <da...@gmail.com> on 2021/10/27 21:56:07 UTC
[Website] .htaccess Rewrite rules not working?
It appears the rewrite rules in camel-website static/.htaccess starting at line 1288 aren’t working. Does anyone know now to investigate what’s going on?
Did they work before the recent latest >> next change?
David Jencks
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
... and the redirects don't seem to work for camel-k, I'll have a fix
shortly, for some reason I did not include camel-k in the tests...
zoran
On Fri, Oct 29, 2021 at 5:14 PM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> happy to say that the tests from the PR below pass on the live site...
>
> zoran
>
> On Fri, Oct 29, 2021 at 3:39 PM Zoran Regvart <zo...@regvart.com> wrote:
> >
> > Hi Cameleers,
> > I've created a PR that I think will solve the issues outlined in this thread:
> >
> > https://github.com/apache/camel-website/pull/659
> >
> > Please have a look, there is a test script there I'd be happy to hear
> > if I missed a test case there, so I can add it and make sure the
> > redirects work as expected.
> >
> > zoran
> > --
> > Zoran Regvart
>
>
>
> --
> Zoran Regvart
--
Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
happy to say that the tests from the PR below pass on the live site...
zoran
On Fri, Oct 29, 2021 at 3:39 PM Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> I've created a PR that I think will solve the issues outlined in this thread:
>
> https://github.com/apache/camel-website/pull/659
>
> Please have a look, there is a test script there I'd be happy to hear
> if I missed a test case there, so I can add it and make sure the
> redirects work as expected.
>
> zoran
> --
> Zoran Regvart
--
Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Antonin,
On Fri, Oct 29, 2021 at 4:10 PM Antonin Stefanutti
<an...@stefanutti.fr.invalid> wrote:
> Naively / intuitively, I would assume 'latest' points to the latest released version, while 'next' points to what is going to be the next version released.
>
> If I understand it correctly, 'latest' is redirected to 'next'.
>
> That being said, I appreciate it may be more complex to implement, if that makes sense at all.
TLDR is that we renamed `latest` to `next`, and we hope to have the
redirects help with that so folk don't end up on a 404 page.
Whether the `latest` or `next` is more appropriate, my 2c on that is
that both are okay, its nuances of semantics. If there is much
opposition to this we can have a debate about it, my 2c again is that
it's not that important.
zoran
--
Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by David Jencks <da...@gmail.com>.
Just so this isn’t left dangling any longer, I came up with https://github.com/apache/camel-website/pull/673 which
- uses Antora to generate the components/latest to components/3.13.x redirects,
- Adds some modified redirectMatch rules to redirect components/ to components/3.13.x
- merges this into the static/.htaccess, removing some old stuff from camel-quarkus and Zoran’s manually written rewrite rules.
This also lets camel projects use the page-aliases feature.
David Jencks
> On Nov 2, 2021, at 2:23 AM, Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi David,
> I'm a bit confused as to what are we trying to achieve here, redirect
> <component>/latest to <component>/<actual latest>, e.g.:
>
> /camel/components/latest to /camel/components/3.12.x
>
> Am I on point thus far? Some questions below:
>
> On Sun, Oct 31, 2021 at 4:26 PM David Jencks <david.a.jencks@gmail.com <ma...@gmail.com>> wrote:
>>
>> I looked into this a little bit, using the Antora 3 `latest-version-segment` feature:
>>
>> urls:
>> redirect_facility: httpd
>> latest_version_segment_strategy: redirect:from
>> latest_version_segment: latest
>>
>> This generates the following in the generated .htaccess:
>>
>> Redirect 302 /manual/latest /manual
>> Redirect 302 /components/latest /components/3.12.x
>> Redirect 302 /camel-k/latest /camel-k/1.6.x
>> Redirect 302 /camel-kamelets/latest /camel-kamelets/next
>> Redirect 302 /camel-quarkus/latest /camel-quarkus/2.4.x
>> Redirect 302 /camel-kafka-connector/latest /camel-kafka-connector/0.11.0
>> Redirect 302 /camel-spring-boot/latest /camel-spring-boot/3.12.x
>> Redirect 302 /camel-karaf/latest /camel-karaf/3.12.x
>> - I think in any case we should use Redirect rather than Rewrite as in fact we want to generate redirects.
>
> Both generate a HTTP redirect, and by that I mean 3xx status and a
> `Location` header, what am I missing here? Btw I would also use
> `Redirect`, it seems easier to follow and maintain.
>
>> - I think we should use 302 rather than 301 since these redirects will change as we release newer versions.
>
> +1 and I think we should do this for both `.../next` and `.../latest` URLs
>
>> - I think that a RedirectMatch rule that redirects <project>/<not concrete version or `next`>/ to the same target is likely to work: such a rule can easily be generated from the above.
>
> Do we need to? Couldn't we use the above generated .htaccess file directly?
>
>> So I’m thinking:
>>
>> - extract the above from the generated .htaccess
>> - transform to the <project> >>> <project>/<latest concrete release> form, and add to generated .htaccess
>> - insert the generated .htaccess in an appropriate place in static .htaccess
>
> Would Antora generate the .htaccess file in the root of the website
> (i.e. in `documentation` and then copied over to `public`) when built,
> so it would overwrite the existing .htaccess file from static? If not,
> i.e. it would generate a .htaccess file per Antora component, we could
> just leave those there.
>
>> I don’t have any good ideas yet on how or where to do this. I imagine the gulp file would be a good place but I’m not an expert on having gulp transform individual files.
>
> So, if I'm understanding this right, the problem is that the two (or
> more?) .htaccess files would be generated in the same location and end
> up overwriting each other. In that case we would need some way of
> merging them and that we can do using Gulp.
>
> Another idea could be to add a Hugo template with similar logic as we
> do on the download page and generate the desired .htaccess file. The
> downloads page is fed via the release note's front matter and _if_ we
> make sure that the documentation is ready for a release, which hasn't
> been the case for 100% of the releases thus far, that's an approach
> that can be made to work.
>
> zoran
> --
> Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi David,
I'm a bit confused as to what are we trying to achieve here, redirect
<component>/latest to <component>/<actual latest>, e.g.:
/camel/components/latest to /camel/components/3.12.x
Am I on point thus far? Some questions below:
On Sun, Oct 31, 2021 at 4:26 PM David Jencks <da...@gmail.com> wrote:
>
> I looked into this a little bit, using the Antora 3 `latest-version-segment` feature:
>
> urls:
> redirect_facility: httpd
> latest_version_segment_strategy: redirect:from
> latest_version_segment: latest
>
> This generates the following in the generated .htaccess:
>
> Redirect 302 /manual/latest /manual
> Redirect 302 /components/latest /components/3.12.x
> Redirect 302 /camel-k/latest /camel-k/1.6.x
> Redirect 302 /camel-kamelets/latest /camel-kamelets/next
> Redirect 302 /camel-quarkus/latest /camel-quarkus/2.4.x
> Redirect 302 /camel-kafka-connector/latest /camel-kafka-connector/0.11.0
> Redirect 302 /camel-spring-boot/latest /camel-spring-boot/3.12.x
> Redirect 302 /camel-karaf/latest /camel-karaf/3.12.x
> - I think in any case we should use Redirect rather than Rewrite as in fact we want to generate redirects.
Both generate a HTTP redirect, and by that I mean 3xx status and a
`Location` header, what am I missing here? Btw I would also use
`Redirect`, it seems easier to follow and maintain.
> - I think we should use 302 rather than 301 since these redirects will change as we release newer versions.
+1 and I think we should do this for both `.../next` and `.../latest` URLs
> - I think that a RedirectMatch rule that redirects <project>/<not concrete version or `next`>/ to the same target is likely to work: such a rule can easily be generated from the above.
Do we need to? Couldn't we use the above generated .htaccess file directly?
> So I’m thinking:
>
> - extract the above from the generated .htaccess
> - transform to the <project> >>> <project>/<latest concrete release> form, and add to generated .htaccess
> - insert the generated .htaccess in an appropriate place in static .htaccess
Would Antora generate the .htaccess file in the root of the website
(i.e. in `documentation` and then copied over to `public`) when built,
so it would overwrite the existing .htaccess file from static? If not,
i.e. it would generate a .htaccess file per Antora component, we could
just leave those there.
> I don’t have any good ideas yet on how or where to do this. I imagine the gulp file would be a good place but I’m not an expert on having gulp transform individual files.
So, if I'm understanding this right, the problem is that the two (or
more?) .htaccess files would be generated in the same location and end
up overwriting each other. In that case we would need some way of
merging them and that we can do using Gulp.
Another idea could be to add a Hugo template with similar logic as we
do on the download page and generate the desired .htaccess file. The
downloads page is fed via the release note's front matter and _if_ we
make sure that the documentation is ready for a release, which hasn't
been the case for 100% of the releases thus far, that's an approach
that can be made to work.
zoran
--
Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by David Jencks <da...@gmail.com>.
I looked into this a little bit, using the Antora 3 `latest-version-segment` feature:
urls:
redirect_facility: httpd
latest_version_segment_strategy: redirect:from
latest_version_segment: latest
This generates the following in the generated .htaccess:
Redirect 302 /manual/latest /manual
Redirect 302 /components/latest /components/3.12.x
Redirect 302 /camel-k/latest /camel-k/1.6.x
Redirect 302 /camel-kamelets/latest /camel-kamelets/next
Redirect 302 /camel-quarkus/latest /camel-quarkus/2.4.x
Redirect 302 /camel-kafka-connector/latest /camel-kafka-connector/0.11.0
Redirect 302 /camel-spring-boot/latest /camel-spring-boot/3.12.x
Redirect 302 /camel-karaf/latest /camel-karaf/3.12.x
- I think in any case we should use Redirect rather than Rewrite as in fact we want to generate redirects.
- I think we should use 302 rather than 301 since these redirects will change as we release newer versions.
- I think that a RedirectMatch rule that redirects <project>/<not concrete version or `next`>/ to the same target is likely to work: such a rule can easily be generated from the above.
So I’m thinking:
- extract the above from the generated .htaccess
- transform to the <project> >>> <project>/<latest concrete release> form, and add to generated .htaccess
- insert the generated .htaccess in an appropriate place in static .htaccess
I don’t have any good ideas yet on how or where to do this. I imagine the gulp file would be a good place but I’m not an expert on having gulp transform individual files.
David Jencks
> On Oct 29, 2021, at 7:40 AM, Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi David,
>
> On Fri, Oct 29, 2021 at 4:24 PM David Jencks <da...@gmail.com> wrote:
>>
>> Well, I agree and am considering how to make that happen. This redirects the previous `latest` links to the same pages which are now at `next` so at least we don’t have broken links (someone pointed one out on Zulip just now).
>>
>> Currently the latest released main camel version is 3.12.x. Taking activemq as an example, there are 3 pages that I think should end up in the same place:
>>
>> https://camel.apache.org/components/activemq-component.html
>> https://camel.apache.org/components/latest/activemq-component.html
>> https://camel.apache.org/components/3.12.x/activemq-component.html
>
> In that case the RewriteRule needs to be changed not to redirect the
> first URL to `/components/next/...`. How would we go about redirecting
> "" and "latest" to 3.12.x, we'd need to compute what the latest
> release is. Which we do in in Hugo bits for the download page
>
>> Antora can produce a rewrite rule (I think) to deal with one redirection. Using this would mean we’d have to incorporate an Antora generated .htaccess into a static one, which would be nice for other reasons, namely we can have working page aliases.
>
> Can Antora help with the above ("" and "latest -> 3.12.x)?
>
>> I don’t think we want to have a manually maintained rewrite rule that directs to the concrete version.
>
> Not at all, this would be error prone and we would forget that it
> needs to be done.
>
>> Which of these should be the URL the other two redirect to? I’d think the one with the concrete version 3.12.x.
>
> 3.12.x makes sense for me, but only if we have a way to auto-maintain
> it, otherwise it's just more work to keep track of...
>
>> Do we actually want all 3 urls to work or can we get by with two?
>
> Not sure, having all three makes sense to me, the first one ("") bit
> less than the others, but if possible I'd still include it...
>
> (2c)
>
> zoran
> --
> Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi David,
On Fri, Oct 29, 2021 at 4:24 PM David Jencks <da...@gmail.com> wrote:
>
> Well, I agree and am considering how to make that happen. This redirects the previous `latest` links to the same pages which are now at `next` so at least we don’t have broken links (someone pointed one out on Zulip just now).
>
> Currently the latest released main camel version is 3.12.x. Taking activemq as an example, there are 3 pages that I think should end up in the same place:
>
> https://camel.apache.org/components/activemq-component.html
> https://camel.apache.org/components/latest/activemq-component.html
> https://camel.apache.org/components/3.12.x/activemq-component.html
In that case the RewriteRule needs to be changed not to redirect the
first URL to `/components/next/...`. How would we go about redirecting
"" and "latest" to 3.12.x, we'd need to compute what the latest
release is. Which we do in in Hugo bits for the download page
> Antora can produce a rewrite rule (I think) to deal with one redirection. Using this would mean we’d have to incorporate an Antora generated .htaccess into a static one, which would be nice for other reasons, namely we can have working page aliases.
Can Antora help with the above ("" and "latest -> 3.12.x)?
> I don’t think we want to have a manually maintained rewrite rule that directs to the concrete version.
Not at all, this would be error prone and we would forget that it
needs to be done.
> Which of these should be the URL the other two redirect to? I’d think the one with the concrete version 3.12.x.
3.12.x makes sense for me, but only if we have a way to auto-maintain
it, otherwise it's just more work to keep track of...
> Do we actually want all 3 urls to work or can we get by with two?
Not sure, having all three makes sense to me, the first one ("") bit
less than the others, but if possible I'd still include it...
(2c)
zoran
--
Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by David Jencks <da...@gmail.com>.
Well, I agree and am considering how to make that happen. This redirects the previous `latest` links to the same pages which are now at `next` so at least we don’t have broken links (someone pointed one out on Zulip just now).
Currently the latest released main camel version is 3.12.x. Taking activemq as an example, there are 3 pages that I think should end up in the same place:
https://camel.apache.org/components/activemq-component.html
https://camel.apache.org/components/latest/activemq-component.html
https://camel.apache.org/components/3.12.x/activemq-component.html
Antora can produce a rewrite rule (I think) to deal with one redirection. Using this would mean we’d have to incorporate an Antora generated .htaccess into a static one, which would be nice for other reasons, namely we can have working page aliases.
I don’t think we want to have a manually maintained rewrite rule that directs to the concrete version.
Which of these should be the URL the other two redirect to? I’d think the one with the concrete version 3.12.x.
Do we actually want all 3 urls to work or can we get by with two?
David Jencks
> On Oct 29, 2021, at 7:10 AM, Antonin Stefanutti <an...@stefanutti.fr.INVALID> wrote:
>
> Naively / intuitively, I would assume 'latest' points to the latest released version, while 'next' points to what is going to be the next version released.
>
> If I understand it correctly, 'latest' is redirected to 'next'.
>
> That being said, I appreciate it may be more complex to implement, if that makes sense at all.
>
>> On 29 Oct 2021, at 15:39, Zoran Regvart <zo...@regvart.com> wrote:
>>
>> Hi Cameleers,
>> I've created a PR that I think will solve the issues outlined in this thread:
>>
>> https://github.com/apache/camel-website/pull/659
>>
>> Please have a look, there is a test script there I'd be happy to hear
>> if I missed a test case there, so I can add it and make sure the
>> redirects work as expected.
>>
>> zoran
>> --
>> Zoran Regvart
>
Re: [Website] .htaccess Rewrite rules not working?
Posted by Antonin Stefanutti <an...@stefanutti.fr.INVALID>.
Naively / intuitively, I would assume 'latest' points to the latest released version, while 'next' points to what is going to be the next version released.
If I understand it correctly, 'latest' is redirected to 'next'.
That being said, I appreciate it may be more complex to implement, if that makes sense at all.
> On 29 Oct 2021, at 15:39, Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi Cameleers,
> I've created a PR that I think will solve the issues outlined in this thread:
>
> https://github.com/apache/camel-website/pull/659
>
> Please have a look, there is a test script there I'd be happy to hear
> if I missed a test case there, so I can add it and make sure the
> redirects work as expected.
>
> zoran
> --
> Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi Cameleers,
I've created a PR that I think will solve the issues outlined in this thread:
https://github.com/apache/camel-website/pull/659
Please have a look, there is a test script there I'd be happy to hear
if I missed a test case there, so I can add it and make sure the
redirects work as expected.
zoran
--
Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi David & Claus,
note the slash before the dollar sign on those, that means that the
URL needs to end with a slash, so:
$ curl -v https://camel.apache.org/components/latest
gives 404, whereas:
$ curl -v https://camel.apache.org/components/latest/
redirects to https://camel.apache.org/components/next/
The source of confusion might be that:
$ curl -v https://camel.apache.org/components
redirects to https://camel.apache.org/components/ and then to
https://camel.apache.org/components/next/
This I think is due to the `DirectorySlash`[1] being set to `On`, most
likely somewhere in the server configuration; and then hitting the
rule used above. Since the `/component/latest` directory no longer
exists the `DirectorySlash` doesn't take effect (no directory), so the
redirect to `/component/latest/` doesn't happen and the rule to
redirect to `/component/next/` doesn't trigger. We could add something
like:
Redirect 301 /components/latest /components/next/
Redirect 301 /camel-spring-boot/latest /camel-spring-boot/next/
Redirect 301 /camel-karaf/latest /camel-karaf/next/
Redirect 301 /camel-k/latest /camel-k/next/
Redirect 301 /camel-kafka-connector/latest /camel-kafka-connector/next/
Redirect 301 /camel-quarkus/latest /camel-quarkus/next/
To cover that case, though not sure where /.../latest (without the
slash) would be linked from, if someone copy-pasted the link from the
address bar in the browser it should already contain the slash at the
end.
There is no rule to redirect
https://camel.apache.org/components/<something> to
https://camel.apache.org/components/next/<something>, so getting a 404
for https://camel.apache.org/components/activemq-component.html is
expected. To be honest, not sure we need such a rule, and it might be
a bit fiddly to add one given that there are sub-directories within
components, that rule if not written carefully could create an endless
loop.
To me more worrying, and as David also notes, is that the rules to
redirect latest to next don't seem to work, i.e.
$ curl -v https://camel.apache.org/components/latest/activemq-component.html
should lead to a redirect to
https://camel.apache.org/components/next/activemq-component.html
I'll have a bit of a look and try to sort this out.
zoran
[1] http://httpd.apache.org/docs/current/mod/mod_dir.html#directoryslash
On Fri, Oct 29, 2021 at 5:33 AM David Jencks <da...@gmail.com> wrote:
>
> Well, that’s not a very useful url… I tried
>
> % curl -k https://camel.apache.org/components/activemq-component.html
> <!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,initial-scale=1"> <title>Page Not Found :: Apache Camel</title> <meta name="generator" content="Antora 3.0.0-alpha…
>
> same for
>
> % curl -k https://camel.apache.org/components/latest/activemq-component.html
>
> I also got the error page for
>
> % curl -k https://camel.apache.org/components/latest
>
> (curl on my mac doesn’t seem to know about any certificates, thus the -k)
>
> This matches the behavior in my browser when I try to use the redirects on an actual page.
>
> David Jencks
>
> > On Oct 28, 2021, at 12:53 PM, Zoran Regvart <zo...@regvart.com> wrote:
> >
> > Hi David,
> > I've tried the one on 1288 line:
> >
> > $ curl https://camel.apache.org/components/
> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> > <html><head>
> > <title>301 Moved Permanently</title>
> > </head><body>
> > <h1>Moved Permanently</h1>
> > <p>The document has moved <a
> > href="https://camel.apache.org/components/next/">here</a>.</p>
> > </body></html>
> >
> > and a couple below it, and it works on my end, a typo at your end?
> >
> > zoran
> >
> > On Wed, Oct 27, 2021 at 11:56 PM David Jencks <da...@gmail.com> wrote:
> >>
> >> It appears the rewrite rules in camel-website static/.htaccess starting at line 1288 aren’t working. Does anyone know now to investigate what’s going on?
> >> Did they work before the recent latest >> next change?
> >>
> >> David Jencks
> >
> >
> >
> > --
> > Zoran Regvart
>
--
Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Claus Ibsen <cl...@gmail.com>.
Hi
I also get an error page for /latest
~/workspace ❯ curl -i https://camel.apache.org/components/latest
HTTP/2 404
On Fri, Oct 29, 2021 at 5:33 AM David Jencks <da...@gmail.com> wrote:
>
> Well, that’s not a very useful url… I tried
>
> % curl -k https://camel.apache.org/components/activemq-component.html
> <!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,initial-scale=1"> <title>Page Not Found :: Apache Camel</title> <meta name="generator" content="Antora 3.0.0-alpha…
>
> same for
>
> % curl -k https://camel.apache.org/components/latest/activemq-component.html
>
> I also got the error page for
>
> % curl -k https://camel.apache.org/components/latest
>
> (curl on my mac doesn’t seem to know about any certificates, thus the -k)
>
> This matches the behavior in my browser when I try to use the redirects on an actual page.
>
> David Jencks
>
> > On Oct 28, 2021, at 12:53 PM, Zoran Regvart <zo...@regvart.com> wrote:
> >
> > Hi David,
> > I've tried the one on 1288 line:
> >
> > $ curl https://camel.apache.org/components/
> > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> > <html><head>
> > <title>301 Moved Permanently</title>
> > </head><body>
> > <h1>Moved Permanently</h1>
> > <p>The document has moved <a
> > href="https://camel.apache.org/components/next/">here</a>.</p>
> > </body></html>
> >
> > and a couple below it, and it works on my end, a typo at your end?
> >
> > zoran
> >
> > On Wed, Oct 27, 2021 at 11:56 PM David Jencks <da...@gmail.com> wrote:
> >>
> >> It appears the rewrite rules in camel-website static/.htaccess starting at line 1288 aren’t working. Does anyone know now to investigate what’s going on?
> >> Did they work before the recent latest >> next change?
> >>
> >> David Jencks
> >
> >
> >
> > --
> > Zoran Regvart
>
--
Claus Ibsen
-----------------
http://davsclaus.com @davsclaus
Camel in Action 2: https://www.manning.com/ibsen2
Re: [Website] .htaccess Rewrite rules not working?
Posted by David Jencks <da...@gmail.com>.
Well, that’s not a very useful url… I tried
% curl -k https://camel.apache.org/components/activemq-component.html
<!doctype html> <html lang="en"> <head> <meta charset="utf-8"> <meta name="viewport" content="width=device-width,initial-scale=1"> <title>Page Not Found :: Apache Camel</title> <meta name="generator" content="Antora 3.0.0-alpha…
same for
% curl -k https://camel.apache.org/components/latest/activemq-component.html
I also got the error page for
% curl -k https://camel.apache.org/components/latest
(curl on my mac doesn’t seem to know about any certificates, thus the -k)
This matches the behavior in my browser when I try to use the redirects on an actual page.
David Jencks
> On Oct 28, 2021, at 12:53 PM, Zoran Regvart <zo...@regvart.com> wrote:
>
> Hi David,
> I've tried the one on 1288 line:
>
> $ curl https://camel.apache.org/components/
> <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
> <html><head>
> <title>301 Moved Permanently</title>
> </head><body>
> <h1>Moved Permanently</h1>
> <p>The document has moved <a
> href="https://camel.apache.org/components/next/">here</a>.</p>
> </body></html>
>
> and a couple below it, and it works on my end, a typo at your end?
>
> zoran
>
> On Wed, Oct 27, 2021 at 11:56 PM David Jencks <da...@gmail.com> wrote:
>>
>> It appears the rewrite rules in camel-website static/.htaccess starting at line 1288 aren’t working. Does anyone know now to investigate what’s going on?
>> Did they work before the recent latest >> next change?
>>
>> David Jencks
>
>
>
> --
> Zoran Regvart
Re: [Website] .htaccess Rewrite rules not working?
Posted by Zoran Regvart <zo...@regvart.com>.
Hi David,
I've tried the one on 1288 line:
$ curl https://camel.apache.org/components/
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>301 Moved Permanently</title>
</head><body>
<h1>Moved Permanently</h1>
<p>The document has moved <a
href="https://camel.apache.org/components/next/">here</a>.</p>
</body></html>
and a couple below it, and it works on my end, a typo at your end?
zoran
On Wed, Oct 27, 2021 at 11:56 PM David Jencks <da...@gmail.com> wrote:
>
> It appears the rewrite rules in camel-website static/.htaccess starting at line 1288 aren’t working. Does anyone know now to investigate what’s going on?
> Did they work before the recent latest >> next change?
>
> David Jencks
--
Zoran Regvart