How to get nested request object from HttpServletRequest https://liferay.dev/c/message_boards/find_thread?p_l_id=119785294&threadId=120839097 2026-04-04T22:30:28Z 2026-04-04T22:30:28Z Olaf Kock https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=121058878 2021-08-19T08:39:16Z 2021-08-19T08:39:15Z

<p>Posting text as image guarantees that it's hard to read. Please don't do that.</p> <p>There are two different methods that reveal a HttpServlerRequests. I've <a href="https://stackoverflow.com/a/9030658/13447">described both options in the past on stackoverflow</a>. Please check that answer</p>

Olaf Kock 2021-08-19T08:39:15Z Brijesh Desai https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=120838662 2021-06-21T18:21:19Z 2021-06-21T18:21:19Z

<p>Hi Olaf,</p> <p>Thanks for details here. Appreciate quick response..!!</p> <p>We have created custom Spring login portlet in Liferay 6.2 with Jboss.</p> <p>We are facing a blocker issue with Login after patch deployment, if we remove patch, same custom login portlet works successfully,</p> <p>Lifeary OOTB login portlet works with and without patch with both condition,</p> <p>When Investigating, Liferay login have 1 level less in nested request object compared to custom login request object, and due to that dispatcherType value are different, with OOTB login dispatcherType is 2 and with custom login portlet dispatcherType value is 4, in Liferay Patch, We compared source code, and found some code difference in LoginUtil  &gt; login method, in Patch src LoginUtil &gt; login method have check with dispatcherType if 2 and executes some code when patch deployed in debug mode, and with custom login portlet, dispatcherType value comes 4 and it doesn't execute some part of code in debug mode.</p> <p>we have custom Login portlet and we are calling Liferay services to authenticate users by following code,</p> <p> <img src="/documents/14/0/Liferay+Login+Auth+service.png/21b45167-27d3-97d2-55ab-6edc18ef25c6?t=1624298709676&amp;imagePreview=1" /></p> <p> </p> <p>Any thoughts or directions will really help us.. thanks in advance.</p> <p>Regards,</p> <p>Brijesh</p>

Brijesh Desai 2021-06-21T18:21:19Z Olaf Kock https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=120840245 2021-06-21T07:16:48Z 2021-06-21T07:16:48Z

<p>No, you don't.</p> <p>This is an implementation detail that could change any time, with any minor update to either Liferay or your appserver.</p> <p>The follow-up question is: <strong>What</strong> do you want to have it <strong>for</strong>? <em>That</em> would be a question that might be answerable. The data (e.g. parameters etc) should be in the request that you already have.</p> <p>Unless I know more about the underlying problem, this smells like a classic x-y-problem to me.</p>

Olaf Kock 2021-06-21T07:16:48Z Brijesh Desai https://liferay.dev/c/message_boards/find_message?p_l_id=119785294&messageId=120839096 2021-08-17T16:24:51Z 2021-06-19T12:36:27Z

<p>Hello All,</p> <p>We have nested object in HttpServletRequest, we need to get child request object highlighted in following screenshot.</p> <p>Please help.</p> <p> <img alt="" src="/documents/14/0/request_debug.png/4653ae90-53cd-d1bc-7052-462fe27ddc59?t=1624106064588&amp;imagePreview=1" /></p> <p> </p> <p>Regards, Brijesh</p>

Brijesh Desai 2021-06-19T12:36:27Z