Talk:Page hijacking

Some sentences here are a possible copvio from [1] so need to be rewritten quickly. (The explanation there isn't great, either: I'm not sure I understand it, a

Talk:Page hijacking

Untitled

Some sentences here are a possible copvio from [1] so need to be rewritten quickly. (The explanation there isn't great, either: I'm not sure I understand it, and I administer several Apache servers. 302 is temporary redirect; I presume the Location header that is returned with the response is the victim page, and the script doesn't provide the content itself?) --Cedderstk 22:45, 18 May 2006 (UTC)Reply

302 Google Jacking → Page hijacking

Hello. I've merged 302 Google Jacking into this article as nobody was against it after waiting 5 days. I hope nobody minds the merge. I've also taken the liberty to clarify the article with a simple example. All the webmasters who edited the article added übernerd jargon which no mortal could understand. Mind you, I'm a webmaster myself but when I showed the original articles to a friend, she was totally lost. I tried my best to make everything more clear, but I'm no expert on this subject since I don't care about my position in search engine results. :) --Zabadab 19:13, 19 July 2006 (UTC)Reply

Merger proposal

I propose that Page hijacking be merged into Phishing. I think that the content in the Page hijacking article can easily be explained in the context of Phishing, and the Phishing article is of a reasonable size that the merging of Page hijacking will not cause any problems as far as article size or undue weight is concerned. FockeWulf FW 190 (talk) 22:08, 24 May 2016 (UTC)Reply

@FockeWulf FW 190: This whole page should be cleared IMO. Worked in web security for around 10 years and "Page hijacking" refers to when a web page is hijacked through a web vulnerability or through other means like a irreputable advertiser script. The vulnerability could be from XSS, Code injection, File inclusion or another web vulnerability. It is not what this page claims i.e. "Page hijacking is a form of search engine index spamming", that is Spamdexing which already has a article. What is in this article isn't even worth merging into another article, just my opinion. Offnfopt(talk) 09:11, 13 June 2016 (UTC)Reply
I don't agree with anything this article says, but if you really wanted to keep the existing content and merge it somewhere then based on what the article claims, it should be merged to the "page hijacking" section on the spamdexing page. Offnfopt(talk) 09:21, 13 June 2016 (UTC)Reply
@Offnfopt:I've removed and altered most of it's content so the article is not as misleading as it once was.It's a start, but is better then it was before.

Also it has occurred that some phishing attacks have used page hijacking to compromise hard to reach targets. FockeWulf FW 190 (talk) 16:30, 13 June 2016 (UTC)Reply

Oppose merger since the article does not have even a single source to support it. All sources I find online are low-effort blog spam. I do support deleting this page and replacing it with a redirect to Phishing to facilitate searches (but without any content move). Anton.bersh (talk) 08:12, 5 April 2021 (UTC)Reply

Deletion of this page

When I search for "Page hijacking" I get a bunch of blog-spam articles which in my opinion don't meet criteria for reliable sources. All of the uses of this term seem to refer to Phishing, which is a notable subject. Therefore I propose deletion of this page with and redirect to Phishing. See prior discussion above. Anton.bersh (talk) 08:16, 5 April 2021 (UTC)Reply

That wasn't going to work as a PROD, which is for "uncontroversial deletions". Suggest putting it at AfD for more input, especially since there are multiple options being talked about here (merger, deletion, rework). --Elmidae (talk · contribs) 20:34, 6 April 2021 (UTC)Reply

Content Disclaimer

Informasi ini disarikan dari Wikipedia dan disajikan kembali untuk tujuan edukasi. Konten tersedia di bawah lisensi CC BY-SA 3.0. Kami tidak bertanggung jawab atas ketidakakuratan data yang bersumber dari kontribusi publik tersebut.

  1. The information displayed on this website is sourced in part or in whole from Wikipedia and has been adapted for the purpose of restating it. We strive to provide accurate and relevant information, however:
  2. There is no guarantee of absolute accuracy. Wikipedia is an open, collaborative project that can be edited by anyone, so information is subject to change.
  3. It is not intended to constitute professional advice. The content displayed is for informational and educational purposes only. For important decisions (e.g., medical, legal, or financial), please consult a professional.
  4. Content copyright. Wikipedia is licensed under the Creative Commons Attribution-ShareAlike License (CC BY-SA). This means that content may be reused with appropriate attribution and shared under a similar license.
  5. Responsible use. Any risk arising from the use of information from this website is entirely the responsibility of the user.