What does the Liferay "http://<domain name>/c" URL really do?What does the Liferay "http://<domain name>/c" URL really do?https://liferay.dev/en/c/message_boards/find_thread?p_l_id=119785333&threadId=733710802024-03-29T09:45:40Z2024-03-29T09:45:40ZRE: What does the Liferay "http://<domain name>/c" URL really do?Ram Sunkahttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=1192028752020-05-20T12:40:52Z2020-05-20T12:40:52ZHello,<br />am using liferay(6.1.2 CE GA3) custom login feature.<br />1. When i hit the localhost:8080/en?USER_ID=Ram,<br />2. request is coming to login() method of LiferayAutoLogin class which implements AutoLogin interface.<br />3. And then request forwarded to login.events.post=com.xxx.xxx.Abc. <br />4. In Abc class, PortalUtil.getCurrentURL(request) is giving "/c". i was expecting "en?USER_ID=Ram".<br />can someone help me here.Ram Sunka2020-05-20T12:40:52ZRE: What does the Liferay "http://<domain name>/c" URL really do?trx xhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=736941642016-04-30T06:37:40Z2016-04-30T06:37:40ZGood explanation. The "http://www.qad.com/c" occurs after completing the post login process right before it returns the user back to it's original page where the user clicked "Login". In the view source code I found that the embedded javascript theme display function shows this URL. <br />I've attached the screenshot. Is there any purpose of this "getPathMain()" function and why does it go to "/c" when that URL is meaningless by itself?<br />We are interested in this URL because it sometimes take the user to a 404 page after logging in and we can't currently pin point why it's happening, but understanding the "/c" URL hopefully can help us narrow down the culprit. <br /><br />Thoughts?<br /><br />Thanks.trx x2016-04-30T06:37:40ZRE: What does the Liferay "http://<domain name>/c" URL really do?Olaf Kockhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=734245762016-04-23T21:17:39Z2016-04-23T21:17:39ZI'd say that Liferay does this because there's nothing available under the URL /c - as David mentions above, it needs some more information - /c is just part of some of the portal internal URLs, but by itself it doesn't have a meaning. You should determine where the link to this URL comes from - if it's actually on the page somewhere, that's a bug. It might also just be a spider that deconstructs legal URLs and checks if it can find something in the individual hierarchy elements - e.g. directory listings.Olaf Kock2016-04-23T21:17:39ZRE: What does the Liferay "http://<domain name>/c" URL really do?trx xhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=734067172016-04-22T22:24:01Z2016-04-22T22:24:01ZHello David,<br /> We've noticed that at times the "c" URL takes the user to a 404 page when logging in. <br /><br />Step 1) http://www.qad.com<br />NOTE: You'll notice "http://www.qad.com/c" before taking the user to the location 404 page (302 code response). <br /><br />Why would Liferay request the "/c" URL and then respond with a 302 code response to the 404 page?<br /><br />Attached picture of headers. <br /><br />Thanks.trx x2016-04-22T22:24:01ZRE: What does the Liferay "http://<domain name>/c" URL really do?David H Nebingerhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=733763912016-04-22T03:03:04Z2016-04-22T03:03:04ZThe /c prefix is a special entry point into the portal. Normally you hit something like /c/portal/login or /c/portal/logout or one of a handful of others. It is typically not a URL pattern that a user will use, but an internal one Liferay will use for internal redirection and other special functions.David H Nebinger2016-04-22T03:03:04ZWhat does the Liferay "http://<domain name>/c" URL really do?trx xhttps://liferay.dev/en/c/message_boards/find_message?p_l_id=119785333&messageId=733710792016-04-22T01:26:24Z2016-04-22T01:26:24ZHello community,<br /> After seeing some strange behavior with Liferay URLs we've noticed that the URL below always sends the user back to it's previous URL. <br />To simplify the issue, below are the same steps: <br /><br />Steps: <br />1) http://www.qad.com/404<br />2) http://www.qad.com/c <br /><br />#2 step always takes the user back to the previous page #1 with a 302 code response (found). <br /><br />My question what does the "/c" URL actually do and why does it behave the way it does?<br /><br />ex) HTTP HEADERS:<br /><br />Request Headers ------> <br />view parsed<br />GET /c HTTP/1.1<br />Host: www.qad.com<br />Connection: keep-alive<br />Pragma: no-cache<br />Cache-Control: no-cache<br />Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8<br />Upgrade-Insecure-Requests: 1<br />User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/49.0.2623.112 Safari/537.36<br />Accept-Encoding: gzip, deflate, sdch<br />Accept-Language: en-US,en;q=0.8<br />Cookie: <br /><br />Response Headers ------> <br />HTTP/1.1 302 Found<br />Date: Fri, 22 Apr 2016 01:23:55 GMT<br />Liferay-Portal: Liferay Portal Enterprise Edition 6.2.10 EE GA1 (Newton / Bui