Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

자세히 살펴보기

Is the mobile version of Mozilla Support no longer functional/supported?

more options

I have been trying to use the mobile version of support.mozilla.org for quite some time (because I use a custom user-agent on my browser, the mobile site is the one that is presented to me by default).

Although I can view posts on the site, I cannot perform any "write" actions (e.g. marking an answer as helpful, marking a question as "I too have this problem", answering a question, or even signing up via the mobile page at https://support.mozilla.org/en-US/users/register?&mobile=1); whenever I try to perform one of the above, I am redirected to a 403 error page stating that I do not have permission to perform that action (for the first 3 examples, even when I am already logged in via my support account; as for the registration, it doesn't make sense at all, as I should not need to possess any "permissions" in order to initiate a signup request).

In fact I am currently typing this post on the mobile "ask a question" page (https://support.mozilla.org/en-US/questions/new/mobile/other/form?search=&step=aaq-question) and I am pretty sure the submission of the question would fail; in that case I would re-post this via the desktop site, stating the fact.

So, in summary, is the mobile site no longer supported, i.e. is it limited to archive-type (view-only) functionality?

I have been trying to use the mobile version of support.mozilla.org for quite some time (because I use a custom user-agent on my browser, the mobile site is the one that is presented to me by default). Although I can view posts on the site, I cannot perform any "write" actions (e.g. marking an answer as helpful, marking a question as "I too have this problem", answering a question, or even signing up via the mobile page at https://support.mozilla.org/en-US/users/register?&mobile=1); whenever I try to perform one of the above, I am redirected to a 403 error page stating that I do not have permission to perform that action (for the first 3 examples, even when I am already logged in via my support account; as for the registration, it doesn't make sense at all, as I should not need to possess any "permissions" in order to initiate a signup request). In fact I am currently typing this post on the mobile "ask a question" page (https://support.mozilla.org/en-US/questions/new/mobile/other/form?search=&step=aaq-question) and I am pretty sure the submission of the question would fail; in that case I would re-post this via the desktop site, stating the fact. So, in summary, is the mobile site no longer supported, i.e. is it limited to archive-type (view-only) functionality?

모든 댓글 (1)

more options

Strangely, the question got posted via the mobile site :)

Still, the other operations remain unusable on the mobile site. For example I just tried marking the "solution" of the following question as helpful, which failed with the same 403 error:

https://support.mozilla.org/en-US/questions/963617


Here's a trace of the request and the response (reconstructed based on info available via the browser):

POST https://support.mozilla.org/en-US/questions/963617/vote/451580

Host: support.mozilla.org User-Agent: Mobile Safari Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8 Accept-Language: en-US,en;q=0.5 Accept-Encoding: gzip, deflate, br Referer: https://support.mozilla.org/en-US/questions/963617 Content-Type: application/x-www-form-urlencoded Content-Length: 15 Cookie: <redacted> Connection: keep-alive Upgrade-Insecure-Requests: 1

helpful=Helpful


HTTP/1.1 403 FORBIDDEN

Server: Apache X-Backend-Server: support1.webapp.phx1.mozilla.com Vary: X-Mobile,User-Agent, Accept-Encoding Content-Type: text/html; charset=utf-8 Content-Encoding: gzip Public-Key-Pins: max-age=1296000; pin-sha256="r/mIkG3eEpVdm+u/ko/cwxzOMo1bk4TyHIlByibiA5E="; pin-sha256="WoiWRyIOVNa9ihaBciRSC7XHjliYS9VwUGOIud4PB18="; Date: Tue, 05 Sep 2017 03:26:39 GMT Keep-Alive: timeout=5, max=1000 Transfer-Encoding: chunked Connection: Keep-Alive Set-Cookie: multidb_pin_writes=y; expires=Tue, 05-Sep-2017 03:26:54 GMT; httponly; Max-Age=15; Path=/ X-Cache-Info: not cacheable; request wasn't a GET or HEAD