Ask Questions and Find Answers

Hello!
We would like to get some help with changing the default redirect status(302) to 301.

Liferay version:  6.2.0-ga1
Java version: 1.7.0_79

What we explored so far is this:
1.  Wrapping the response to a custom object via filter and overriding the sendRedirect method

public class ServletResponseWrapperFilter implements Filter {

    private static final Logger LOG = LoggerFactory.getLogger(ServletResponseWrapperFilter.class);

    @Override
    public void init(FilterConfig filterConfig) throws ServletException {
    }

    @Override
    public void doFilter(ServletRequest request, ServletResponse response, FilterChain chain) throws IOException, ServletException {
        ResponseStatusChangerWrapper wrap = new ResponseStatusChangerWrapper((HttpServletResponse) response);
        chain.doFilter(request, wrap);
    }

    @Override
    public void destroy() {
    }
}

where ResponseStatusChangerWrapper is 

public class ResponseStatusChangerWrapper extends HttpServletResponseWrapper {

    public ResponseStatusChangerWrapper(HttpServletResponse httpServletResponse) {
        super(httpServletResponse);
    }

    @Override
    public void sendRedirect(String location) {
        this.setStatus(301);
        this.setHeader("Location", location);
    }

}

and registering the filter right after the Absolute Redirects Filter

<servlet-filter>
   <servlet-filter-name>Response Status Wrapper Filter</servlet-filter-name>
   <servlet-filter-impl>...ServletResponseWrapperFilter</servlet-filter-impl>
</servlet-filter>
<servlet-filter-mapping>
   <servlet-filter-name>Response Status Wrapper Filter</servlet-filter-name>
   <after-filter>Absolute Redirects Filter</after-filter>
   <url-pattern>/*</url-pattern>
   <dispatcher>REQUEST</dispatcher>
   <dispatcher>FORWARD</dispatcher>
</servlet-filter-mapping>

2. Using the ext plugin

Created from archetype(we are using maven)

<groupid>com.liferay.maven.archetypes</groupid>
<artifactid>liferay-ext-archetype</artifactid>
<version>6.2.0-ga1</version>

Where we altered the AbsoluteRedirectsResponse 
via the plugin-impl module

package com.liferay.portal.servlet.filters.absoluteredirects;

import com.liferay.portal.util.PortalUtil;
import java.io.IOException;
import javax.servlet.http.HttpServletRequest;
import javax.servlet.http.HttpServletResponse;
import javax.servlet.http.HttpServletResponseWrapper;

public class AbsoluteRedirectsResponse extends HttpServletResponseWrapper {
    private HttpServletRequest _request;

    public AbsoluteRedirectsResponse(HttpServletRequest request, HttpServletResponse response) {
        super(response);
        this._request = request;
    }

    public void sendRedirect(String redirect) throws IOException {
        redirect = PortalUtil.getAbsoluteURL(this._request, redirect);
        this._request.setAttribute(AbsoluteRedirectsResponse.class.getName(), redirect);
        // super.sendRedirect(redirect);
        this.setStatus(301);
        this.setHeader("Location", redirect);
    }
}

While #1 gets the job done we are not sure how safe it is. From what we have seen, the initial sendRedirect  is sent from com.liferay.portal.kernel.servlet.MetaInfoCacheServletResponse

public void sendRedirect(String location) throws IOException {
    if (this.isCommitted()) {
        throw new IllegalStateException("Send redirect after commit");
    } else {
        this.resetBuffer(true);
        this.setStatus(302);
        this._metaData._location = location;
        this._committed = true;
        super.sendRedirect(location);
    }
}

With #2,  we do not like the maintenance and extra complexity for removal/update and If it is possible, we would like to avoid it.
We would greatly appreciate any help.