| Stefan Ritt wrote: |
|
| Tom C wrote: |
|
My elog is named "Whatever Elog" so the URL generated is /Whatever+Elog . This works fine but when in the interface certain buttons generate this URL : /Whatever%20Elog ...this URL fails. It seems that elog does not recognize these ( + and %20 ) as the same which I believe they should be as part of HTTP request.
|
Can you be a bit more specific which buttons you mean? The demo logbook https://midas.psi.ch/elogs/Linux+Demo/ has also a space and I cannot see any problem there.
|
Years ago I had a similar issue, although I cannot remember the exact details now. The consequence is that I don't leave any spaces in the log book names. However, I did find that '&' was fine, and the ampersand and %26 are interchangeable in a logbook page, so one logbook is ECP&SIW, and using ampersand or '%26' work interchangably when making llinks from other logbooks to ECP&SIW (that is elog:ECP&SIW or elog:ECP%26SIW work equally well).. This is not true of elog.cfg, where only the actual character should be used. This may be true for some other urlencoded characters.
It may be of note that %20 and '+' are not the same urlencode and character - %20 is a space, '+' is %2B, and a brief bit of playing around shows that elog is not so tolerant of those characters as it is with & and %26, and I crashed mine several times but I was only playing, nothing serious was lost. |