You need to provide a valid URL; your browser is a lot more tolerant about what characters it accepts, but when I copy the URL from the Chrome location bar I get the real URL:

https://plus.google.com/+Rub%C3%A9nRivera

Note the %C3 and %A9 parts; those are UTF-8 bytes encoded using URL percent encoding. The C3 A9 bytes encode a é character.

Using the URL with percent encoding works fine.

Note that Stack Exchange cannot accept 'human readable' URLs because there is no standard encoding to be used. Google+ uses UTF-8, as do a lot of sites, but there is no RFC specification to state what encoding to use here. See What every web developer must know about URL encoding.

You need to provide a valid URL; your browser is a lot more tolerant about what characters it accepts, but when I copy the URL from the Chrome location bar I get the real URL:

https://plus.google.com/+Rub%C3%A9nRivera

Note the %C3 and %A9 parts; those are UTF-8 bytes encoded using URL percent encoding. The C3 A9 bytes encode a é character.

Using the URL with percent encoding works fine.

Note that Stack Exchange cannot accept 'human readable' URLs because there is no standard encoding to be used. Google+ uses UTF-8, as do a lot of sites, but there is no RFC specification to state what encoding to use here. See What every web developer must know about URL encoding. A lone URL doesn't provide enough context for Stack Exchange to determine the correct codec to use.

You need to provide a valid URL; your browser is a lot more tolerant about what characters it accepts, but when I copy the URL from the Chrome location bar I get the real URL:

https://plus.google.com/+Rub%C3%A9nRivera

Note the %C3 and %A9 parts; those are UTF-8 bytes encoded using URL percent encoding. The C3 A9 bytes encode a é character.

Using the URL with percent encoding works fine.

You need to provide a valid URL; your browser is a lot more tolerant about what characters it accepts, but when I copy the URL from the Chrome location bar I get the real URL:

https://plus.google.com/+Rub%C3%A9nRivera

Note the %C3 and %A9 parts; those are UTF-8 bytes encoded using URL percent encoding. The C3 A9 bytes encode a é character.

Using the URL with percent encoding works fine.

Note that Stack Exchange cannot accept 'human readable' URLs because there is no standard encoding to be used. Google+ uses UTF-8, as do a lot of sites, but there is no RFC specification to state what encoding to use here. See What every web developer must know about URL encoding.