wrong url encoding in browser window and comment notifications emails

Hy,
while working with upsource, we are getting wrong urls displayed in the browser

We are seing URL like this in the browser windows:

http://upsource/project/file/c220d45d589307acfed601bcfee4586fc4bd349a/src%2Fmain%2Fjava%2F.....

Copy/pasting the url into a new windows returns a "404 Not Found".

After manual URL-decoding, the url is working:

http://upsource.pch.etat.lu/project/file/c220d45d589307acfed601bcfee4586fc4bd349a/src/main/java/


We have also this "wrong" URL in the emails of the comment notifications.

Thanks,
Tom

6 comments

Tom,

Do you have any proxy configured for Upsource server?

What value does base-url= property have in bundle.properties file located under \Upsource\conf\internal ?

0

\Upsource\conf\internal\bundle.properties

base-url=http\://upsource.pch.etat.lu


the proxy config ( /etc/httpd/conf.d/upsource.conf)


<VirtualHost *:80>
        ServerName upsource.xxxxxxx
        RewriteEngine On

        RewriteCond %{QUERY_STRING} transport=polling
        RewriteRule /(.*)$ http://127.0.0.1:8080/$1 [P]

        ProxyRequests off
        ProxyPass /~socket.io/ ws://127.0.0.1:8080/~socket.io/
        ProxyPassReverse /~socket.io/ ws://127.0.0.1:8080/~socket.io/

        ProxyPass / http://localhost:8080/
        ProxyPassReverse / http://localhost:8080/

        ErrorLog logs/upsource-error_log
        CustomLog logs/upsource-access_log common
</VirtualHost>

Thanks,
Tom

0

More details about the environment:
   Apache 2.4.6 running under CentOS Linux release 7.1.1503 (Core)

0

Tom,

In the apache config file replace localhost with ip address - 127.0.0.1. So it should look like this:

ProxyPass / http://127.0.0,1:8080/
ProxyPassReverse / http://l127.0.0.1:8080/ 

And also add the following line somewhere in <virtual host> block:

AllowEncodedSlashes On



Please let me know if it helps.

0

Yes, it's working now.
The AllowEncodedSlashes On did it working.

Just saw that it's also indicated in the docu. Did you updated it already or did I missed it?

Thanks for your help,
Tom

0

It was updated a week ago. So it depends on when you configured it.

Best regards,
Artem

0

Please sign in to leave a comment.