Check if you didn't set RequestProperty Content-Type to the wrong type or if you're trying to send the wrong file to the server.

You have a different solution? A short tip here would help you and many other users who saw this issue last week.

  • Publishing Issue
    via by 3002728,
  • Publication failed
    via by Nelash Jindal,
  • Publication successful but gices error in logs
    via by Nelash Jindal,
  • Errors on the delivery System
    via by rvillamarin,
  • 401 error on LInkedIn Discussions
    via Stack Overflow by prashant
    • Server returned HTTP response code: 403 for URL: http://xxx.xx.xx.xx:xxxx/cas/v1/tickets/TGT-23-Pe2lSECpekRz4i1pjY6ACAti5MebbX4RPJIoU3hdejJIKjrLtX-cas- xxx.xx.xx.xx:xxxx at at com.fatwire.wem.sso.cas.CASProvider.getST( at com.fatwire.wem.sso.cas.CASProvider.getTicket( at COM.FutureTense.Security.SecureLogin.SecureLoginFilter.doFilter( at weblogic.servlet.internal.FilterChainImpl.doFilter( at COM.FutureTense.Servlet.URLRewriteFilter.doFilter( at weblogic.servlet.internal.FilterChainImpl.doFilter( at com.fatwire.wem.sso.cas.filter.CASFilter.doFilter( at com.fatwire.wem.sso.SSOFilter.doFilter( at weblogic.servlet.internal.FilterChainImpl.doFilter( at com.digi.telenor.login.filter.ConnectIdFilter.doFilter( at weblogic.servlet.internal.FilterChainImpl.doFilter( at weblogic.servlet.internal.WebAppServletContext$ServletInvocationAction.wrapRun( at weblogic.servlet.internal.WebAppServletContext$ at at at weblogic.servlet.internal.WebAppServletContext.securedExecute( at weblogic.servlet.internal.WebAppServletContext.execute( at at at

    Users with the same issue

    1 times, last one,
    10 times, last one,
    Unknown UserUnknown User
    1 times, last one,
    4 times, last one,
    Unknown visitor
    Unknown visitor2 times, last one,
    74 more bugmates