When a user tries to confirm a friend request, they get the red box 'Requests is temporarily unavailable' error message. And the following messages are written to the logs when this happens:

2011-06-20 10:37:09,481 <TP-Processor15> WARN [PortletRequestProcessor:160] - This URL can only be invoked using POST: /web/<user_name>/profile?p_auth=gt9D9F8B&p_p_id=121&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_pos=1&p_p_col_count=2&_121_struts_action=%2Frequests%2Fupdate_request&_121_redirect=http%3A%2F%2F<domain_name>%2Fweb%2F<user_name>%2Fprofile%3Fp_p_id%3D121%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-2%26p_p_col_pos%3D1%26p_p_col_count%3D2&_121_requestId=1604&_121_status=1
2011-06-20 10:37:09,567 <TP-Processor15> ERROR [jsp:154] - com.liferay.portal.security.auth.PrincipalException: /web/<user_name>/profile?p_auth=gt9D9F8B&p_p_id=121&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-2&p_p_col_pos=1&p_p_col_count=2&_121_struts_action=%2Frequests%2Fupdate_request&_121_redirect=http%3A%2F%2F<domain_name>%2Fweb%2F<user_name>%2Fprofile%3Fp_p_id%3D121%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-2%26p_p_col_pos%3D1%26p_p_col_count%3D2&_121_requestId=1604&_121_status=1
at com.liferay.portal.struts.PortletRequestProcessor.process(PortletRequestProcessor.java:165)
at com.liferay.portlet.StrutsPortlet.processAction(StrutsPortlet.java:186)
at com.liferay.portlet.FilterChainImpl.doFilter(FilterChainImpl.java:70)
at com.liferay.portal.kernel.portlet.PortletFilterUtil.doFilter(PortletFilterUtil.java:48)
at com.liferay.portlet.InvokerPortletImpl.invoke(InvokerPortletImpl.java:652)
at com.liferay.portlet.InvokerPortletImpl.invokeAction(InvokerPortletImpl.java:687)
at com.liferay.portlet.InvokerPortletImpl.processAction(InvokerPortletImpl.java:360)
at com.liferay.portal.action.LayoutAction.processPortletRequest(LayoutAction.java:784)
at com.liferay.portal.action.LayoutAction.processLayout(LayoutAction.java:582)
at com.liferay.portal.action.LayoutAction.execute(LayoutAction.java:232)
at org.apache.struts.action.RequestProcessor.processActionPerform(RequestProcessor.java:431)
at org.apache.struts.action.RequestProcessor.process(RequestProcessor.java:236)
at com.liferay.portal.struts.PortalRequestProcessor.process(PortalRequestProcessor.java:153)
at org.apache.struts.action.ActionServlet.process(ActionServlet.java:1196)
at org.apache.struts.action.ActionServlet.doGet(ActionServlet.java:414)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:617)
at com.liferay.portal.servlet.MainServlet.callParentService(MainServlet.java:508)
at com.liferay.portal.servlet.MainServlet.service(MainServlet.java:485)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

This seems to happen randomly for most users, but very consistently for one of our high-profile users!

Anyone else encountered this error and/or have a solution for it?

Thanks,
Jeremy

Now it seems to be even more random than before. I just logged into one browser with a user, clicked confirm, and got the error. I logged out, closed the browser, opened another and different browser, logged in as the user again, clicked confirm again, and it worked just fine! What the heck?

Ticket created for this issue: http://issues.liferay.com/browse/LPS-18312

We have just encountered this problem. What I found interesting is that in our apache logs we see:
- the request coming in as a POST and getting a redirect (302 )back.
- then the request comes in as a GET. At this time the catalina.out contains the same error you see.

Only one client has encountered this problem. As of now, we have not been able to reproduce it. I am hoping to hear back about the browser version that was being used. I am trying to look into this further to find out why a redirect is coming back.

Here are the apache logs containing the redirect.

XX.XXX.XXX.XXX - - [10/Jul/2011:11:13:59 -0400] "POST /member-home?p_auth=ihk7ZSGF&p_p_id=121&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=2&p_p_col_count=4&_121_struts_action=%2Frequests%2Fupdate_request&_121_redirect=http%3A%2F%2FXXX.XXX.XX%2Fmember-home%3Fp_p_id%3D121%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_pos%3D2%26p_p_col_count%3D4&_121_requestId=2402&_121_status=1 HTTP/1.1" 302 - "http://XXX.XXX.XX/member-home" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0)"
XX.XXX.XXX.XXX - - [10/Jul/2011:11:13:59 -0400] "GET /member-home?p_auth=ihk7ZSGF&p_p_id=121&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=2&p_p_col_count=4&_121_struts_action=%2Frequests%2Fupdate_request&_121_redirect=http%3A%2F%2FXXX.XXX.XX%2Fmember-home%3Fp_p_id%3D121%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_pos%3D2%26p_p_col_count%3D4&_121_requestId=2402&_121_status=1 HTTP/1.1" 200 9190 "http://XXX.XXX.XX/member-home" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0)"
XX.XXX.XXX.XXX - - [10/Jul/2011:11:14:00 -0400] "GET /html/themes/classic/images/messages/error.png HTTP/1.1" 200 701 "http://XXX.XXX.XX/member-home?p_auth=ihk7ZSGF&p_p_id=121&p_p_lifecycle=1&p_p_state=normal&p_p_mode=view&p_p_col_id=column-1&p_p_col_pos=2&p_p_col_count=4&_121_struts_action=%2Frequests%2Fupdate_request&_121_redirect=http%3A%2F%2FXXX.XXX.XX%2Fmember-home%3Fp_p_id%3D121%26p_p_lifecycle%3D0%26p_p_state%3Dnormal%26p_p_mode%3Dview%26p_p_col_id%3Dcolumn-1%26p_p_col_pos%3D2%26p_p_col_count%3D4&_121_requestId=2402&_121_status=1" "Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; Win64; x64; Trident/5.0)"

We have reproduced this once here with IE 8, and several times with IE 9.

When you click on the 'accept' link it should send it as a POST. However, sometimes it doesn't send it as a post. This seems to happen if the page isn't completely loaded before you click. On IE 9, often a bar at the bottom asking about secure/insecure content will prevent the page from finishing loading. When this happens the request gets sent as a GET instead of a POST.

I am also getting same red box error on IE9 for Friend request portlet. Any one able to resolve friend request issue?

When a user tries to confirm/accept a friend request on IE8 it work fine b it on IE9 getting red box 'Requests is temporarily unavailable' error message.

Hi Kavita,

Instead of having "liferay-ui:icon" tag library, use simple FORM and create a button inside the form to confirm the friend.

Specify the FORM method=POST
Give FORM action=portletURL (which is already there)
It will always send data in POST way.

Thanks.

It worked. Thanks Vikas

Hey,

I am working on liferay 6.0.6. Can you tell me where to look for all the friend requests that you need to confirm/accept?

There is a portlat called Friend request.

Try the following file:
\social-networking-portlet\summary\view_user.jspf