 | | Re: Multilingual webserver
|
|
(...) I think it would at least require an external rewriting program just to handle the mapping of the accepted and available language to a selected language. And I can't see how you can avoid infinite loops using the Apache rewritemap directive. (...) (19 years ago, 7-Jan-06, to lugnet.off-topic.geek)
|
| |
| | Re: Multilingual webserver
|
|
(...) Yes, you use an external script for the mapping... But it is a fairly simple perl script. And the infinite loops are avoided by having the actual URLs be off a separate tree - /lego/dat/model.dat could be rewritten as (...) (19 years ago, 7-Jan-06, to lugnet.off-topic.geek)
|
| |
| | Re: Multilingual webserver
|
|
(...) But what would I then do if somebody made links to /real-files? (...) But Apache is still written in C. I have already written my own special-purpose web-servers a few times, so it is not something I haven't tried before. And I trust my own (...) (19 years ago, 9-Jan-06, to lugnet.off-topic.geek)
|
| |
| | Re: Multilingual webserver
|
|
(...) Well, first of all no one would ever see /real-files in any url or location bar, so they wouldn't know to link to it. And anyway it is easy to set up access such that direct requests to that URI would be denied - accept only 'subrequests', as (...) (19 years ago, 9-Jan-06, to lugnet.off-topic.geek)
|
| |
| | Re: Multilingual webserver
|
|
(...) But my point is that people should _see_ a URL in the same language as the page. Hiding it inside Apache would be no fun. Play well, Jacob (19 years ago, 9-Jan-06, to lugnet.off-topic.geek)
|
| |
| | Re: Multilingual webserver
|
|
(...) Right - the subrequests aren't visible to the user, so they would never see the /real-files - only the URI in their local language. I guess the first check the mapper would have to do is compare the URI with the desired language, and if they (...) (19 years ago, 9-Jan-06, to lugnet.off-topic.geek)
|
